Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “relational databases”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 37 records · Page 2

A high performance, ad-hoc, fuzzy query processing system for relational databases

Database queries involving imprecise or fuzzy predicates are currently an evolving area of academic and industrial research. Such queries place severe stress on the indexing and I/O subsystems of conventional database environments since they involve the search of large numbers of records. The Datacycle architecture and research prototype is a database environment that uses filtering technology to perform an efficient, exhaustive search of an entire database. It has recently been modified to include fuzzy predicates in its query processing. The approach obviates the need for complex index structures, provides unlimited query throughput, permits the use of ad-hoc fuzzy membership functions, and provides a deterministic response time largely independent of query complexity and load. This paper describes the Datacycle prototype implementation of fuzzy queries and some recent performance results.

Mansfield, William H., Jr.↗

Web interfaces to relational databases

This reports on a project to extend the capabilities of a Virtual Research Center (VRC) for NASA's Advanced Concepts Office. The work was performed as part of NASA's 1995 Summer Faculty Fellowship program and involved the development of a prototype component of the VRC - a database system that provides data creation and access services within a room of the VRC. In support of VRC development, NASA has assembled a laboratory containing the variety of equipment expected to be used by scientists within the VRC. This laboratory consists of the major hardware platforms, SUN, Intel, and Motorola processors and their most common operating systems UNIX, Windows NT, Windows for Workgroups, and Macintosh. The SPARC 20 runs SUN Solaris 2.4, an Intel Pentium runs Windows NT and is installed on a different network from the other machines in the laboratory, a Pentium PC runs Windows for Workgroups, two Intel 386 machines run Windows 3.1, and finally, a PowerMacintosh and a Macintosh IIsi run MacOS.

Carlisle, W. H.↗

Use of HSM with Relational Databases

Hierarchical storage management (HSM) systems have evolved to become a critical component of large information storage operations. They are built on the concept of using a hierarchy of storage technologies to provide a balance in performance and cost. In general, they migrate data from expensive high performance storage to inexpensive low performance storage based on frequency of use. The predominant usage characteristic is that frequency of use is reduced with age and in most cases quite rapidly. The result is that HSM provides an economical means for managing and storing massive volumes of data. Inherent in HSM systems is system managed storage, where the system performs most of the work with minimum operations personnel involvement. This automation is generally extended to include: backup and recovery, data duplexing to provide high availability, and catastrophic recovery through use of off-site storage.

Breeden, Randall↗

SoK: What does it Mean to Benchmark Database Forensics?

Relational Database Management Systems are the backbone of modern enterprises and public-sector services, and are thus frequent targets of security incidents, insider threats, and thorough regulatory audits. Consequently, databases have become key sources of digital evidence, requiring investigators to reconstruct past activity from audit logs, transaction logs, and backups. Although benchmarking frameworks such as those developed by the Transaction Processing Performance Council (TPC) are widely used to evaluate database performance, they do not capture forensic requirements such as evidentiary completeness, tamper-evidence, chain of custody, or regulatory compliance under GDPR and CCPA. This survey examines the emerging domain of forensic database benchmarking. We gathered prior research on database forensics, secure logging, and tamper-evident data structures; we analyze modern forensic-ready features in commercial and open-source systems (SQL Server Ledger, Oracle Blockchain Tables, PostgreSQL pgAudit, Db2 Audit, Aurora Database Activity Streams, Oracle Real Application Security and IBM Guardium) and assess why existing benchmarks are insufficient. We propose forensic workloads, metrics, and methodologies that incorporate adversarial stressors, deleted-record recovery, and backup analysis. We also identify open research problems and call for a community-driven forensic benchmark suite. The result is an idea for evaluating not only database performance but also forensic soundness, bridging the gap between system engineering, compliance, and digital investigations.

Lenard, Ben↗

Extending the Blockchain: Ensuring Transactional Integrity in Relational Data via Blockchain Technology

The idea of combining a relational database with concepts associated with blockchain technology is being examined. The use case outlined herein concurrently utilizes relational and blockchain data structures to facilitate the sharing of complex data among untrusted users without the participation of a trusted third party. By capturing the transactions that result in data being stored in a relational database and placing those transactions in a blockchain structure, users can be assured that the information has not been created, altered, or destroyed without the knowledge of all users of the data. Capturing relational database transactions via a blockchain structure presents several challenges. Among them are increased storage capacity requirements, transaction ordering prior to placement on the blockchain within a multiuser database, use of existing or creation of new consensus mechanisms, and timely data verification. Addressing these challenges, although not unsurmountable, will introduce trade-offs (e.g., increased system sizing, slower transaction execution) that might or might not be acceptable based upon the envisioned use. If these trade-offs are acceptable, then this concept of extending the blockchain is a powerful method to provide both applications and their users immutable, trusted, well-defined, and consistent data.

Ray, Brian↗

StarView: The object oriented design of the ST DADS user interface

StarView is the user interface being developed for the Hubble Space Telescope Data Archive and Distribution Service (ST DADS). ST DADS is the data archive for HST observations and a relational database catalog describing the archived data. Users will use StarView to query the catalog and select appropriate datasets for study. StarView sends requests for archived datasets to ST DADS which processes the requests and returns the database to the user. StarView is designed to be a powerful and extensible user interface. Unique features include an internal relational database to navigate query results, a form definition language that will work with both CRT and X interfaces, a data definition language that will allow StarView to work with any relational database, and the ability to generate adhoc queries without requiring the user to understand the structure of the ST DADS catalog. Ultimately, StarView will allow the user to refine queries in the local database for improved performance and merge in data from external sources for correlation with other query results. The user will be able to create a query from single or multiple forms, merging the selected attributes into a single query. Arbitrary selection of attributes for querying is supported. The user will be able to select how query results are viewed. A standard form or table-row format may be used. Navigation capabilities are provided to aid the user in viewing query results. Object oriented analysis and design techniques were used in the design of StarView to support the mechanisms and concepts required to implement these features. One such mechanism is the Model-View-Controller (MVC) paradigm. The MVC allows the user to have multiple views of the underlying database, while providing a consistent mechanism for interaction regardless of the view. This approach supports both CRT and X interfaces while providing a common mode of user interaction. Another powerful abstraction is the concept of a Query Model. This concept allows a single query to be built form a single or multiple forms before it is submitted to ST DADS. Supporting this concept is the adhoc query generator which allows the user to select and qualify an indeterminate number attributes from the database. The user does not need any knowledge of how the joins across various tables are to be resolved. The adhoc generator calculates the joins automatically and generates the correct SQL query.

Williams, J. D.↗

Methods and apparatus for constructing and implementing a universal extension module for processing objects in a database

Methods and apparatus for providing a multi-tier object-relational database architecture are disclosed. In one illustrative embodiment of the present invention, a multi-tier database architecture comprises an object-relational database engine as a top tier, one or more domain-specific extension modules as a bottom tier, and one or more universal extension modules as a middle tier. The individual extension modules of the bottom tier operationally connect with the one or more universal extension modules which, themselves, operationally connect with the database engine. The domain-specific extension modules preferably provide such functions as search, index, and retrieval services of images, video, audio, time series, web pages, text, XML, spatial data, etc. The domain-specific extension modules may include one or more IBM DB2 extenders, Oracle data cartridges and/or Informix datablades, although other domain-specific extension modules may be used.

Li, Chung-Sheng↗

Generic National Nuclear Forensics Library Implementation

This document provides instructions for the database implementation for national nuclear forensic library (NNFL) using a relational database. While there are many software options that can be used to implement an NNFL database, in this document we reference an Oracle database for the implementation. The principles related here can be applied to any relational database structure. The design revolves around two main types of data: Samples and Results. Samples are materials or descriptions of materials; results are the results of analyses of those samples. All additional tables exist as a result of the normalization process. The remaining tables/entities have keys that are referenced by the Result/Sample tables via foreign key constraints. This allows for the enforcement of different relationships between the tables such as one-to-one, one-to-many, many-to-many. This process helps to ensure that valid data is entered, optimizes database performance and avoids data redundancies.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

SmallSat Database

The SmallSat has an unrealized potential in both the private industry and in the federal government. Currently over 70 companies, 50 universities and 17 governmental agencies are involved in SmallSat research and development. In 1994, the U.S. Army Missile and Defense mapped the moon using smallSat imagery. Since then Smart Phones have introduced this imagery to the people of the world as diverse industries watched this trend. The deployment cost of smallSats is also greatly reduced compared to traditional satellites due to the fact that multiple units can be deployed in a single mission. Imaging payloads have become more sophisticated, smaller and lighter. In addition, the growth of small technology obtained from private industries has led to the more widespread use of smallSats. This includes greater revisit rates in imagery, significantly lower costs, the ability to update technology more frequently and the ability to decrease vulnerability of enemy attacks. The popularity of smallSats show a changing mentality in this fast paced world of tomorrow. What impact has this created on the NASA communication networks now and in future years? In this project, we are developing the SmallSat Relational Database which can support a simulation of smallSats within the NASA SCaN Compatability Environment for Networks and Integrated Communications (SCENIC) Modeling and Simulation Lab. The NASA Space Communications and Networks (SCaN) Program can use this modeling to project required network support needs in the next 10 to 15 years. The SmallSat Rational Database could model smallSats just as the other SCaN databases model the more traditional larger satellites, with a few exceptions. One being that the smallSat Database is designed to be built-to-order. The SmallSat database holds various hardware configurations that can be used to model a smallSat. It will require significant effort to develop as the research material can only be populated by hand to obtain the unique data required. When completed it will interface with the SCENIC environment to allow modeling of smallSats. The SmallSat Relational Database can also be integrated with the SCENIC Simulation modeling system that is currently in development. The SmallSat Relational Database simulation will be of great significance in assisting the NASA SCaN group to understand the impact the smallSats have made which have populated the lower orbit around our mother earth. What I have created and worked on this summer session 2015, is the basis for a tool that will be of value to the NASA SCaN SCENIC Simulation Environment for years to come.

Small Satellites↗

Social media based NPL system to find and retrieve ARM data: Concept paper

Information connectivity and retrieval has a role in our daily lives. The most pervasive source of online information is databases. The amount of data is growing at rapid rate and database technology is improving and having a profound effect. Almost all online applications are storing and retrieving information from databases. One challenge in supplying the public with wider access to informational databases is the need for knowledge of database languages like Structured Query Language (SQL). Although the SQL language has been published in many forms, not everybody is able to write SQL queries. Another challenge is that it may not be practical to make the public aware of the structure of the database. There is a need for novice users to query relational databases using their natural language. To solve this problem, many natural language interfaces to structured databases have been developed. The goal is to provide more intuitive method for generating database queries and delivering responses. Social media makes it possible to interact with a wide section of the population. Through this medium, and with the help of Natural Language Processing (NLP) we can make the data of the Atmospheric Radiation Measurement Data Center (ADC) more accessible to the public. We propose an architecture for using Apache Lucene/Solr [1], OpenML [2,3], and Kafka [4] to generate an automated query/response system with inputs from Twitter5, our Cassandra DB, and our log database. Using the Twitter API and NLP we can give the public the ability to ask questions of our database and get automated responses.

Devarakonda, Ranjeet↗

Technical Evaluation Report for the NDMAS AGR-5/6/7 TRISO Irradiation Monitoring System

The Nuclear Data Management and Analysis System (NDMAS) manages irradiation experiment data collected under the Advanced Gas Reactor (AGR) Fuel Development and Qualification program within the Advanced Reactor Technologies Technology Development Office. The AGR-5/6/7 irradiation experiment combines the fifth, sixth, and seventh planned irradiation campaigns of the U.S. Department of Energy AGR Fuel Development and Qualification Program. These combined irradiation tests will consist of fuel qualification tests (AGR-5/6) and a margin test (AGR-7) for the industrially produced uranium oxycarbide (UCO) tristructural isotropic (TRISO) coated particle fuel developed by the AGR program. The objective of the AGR-5/6/7 irradiation experiment is to establish the performance of UCO TRISO fuel fabricated using engineering-scale equipment in a production environment under and beyond normal operating conditions (PNL-5245). Experimental irradiation measurements for this experiment (i.e., thermocouple temperature, gas flow rate, fission product release rate, gross gamma count, and Advanced Test Reactor (ATR) operational parameters) are captured automatically to the NDMAS database. Data derived from numerical simulation or other mathematical analyses (i.e., fast fluence, burnup, temperature, and fission product release to birth ratio) are captured to the database when provided by the researchers. The NDMAS database is a relational database accessed via structured query language and managed with Microsoft SQL Server. While select users can directly access the database, that is not the most convenient way to interact with the data. The NDMAS team constructs numerous tables that combine related datasets, and delivers those data to researchers via graphs and spreadsheets on a Microsoft SharePoint-based website. For the AGR-5/6/7 experimental data, a new subsite has been developed, along with a set of web pages. These pages will be used by members of fuel irradiation team for monitoring irradiation conditions according to specification (SPC-1749), by the physics modelers to access necessary model inputs, and by the nuclear engineering community to view and access data such as fuel temperatures, fission product release from capsules, and ATR operational parameters. The deliverable represented in this document is a SharePoint website containing tables of the AGR-5/6/7 measured and calculated data, graphs displaying the data, and links to source documents and references.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

AGR-5/6/7 Irradiation Monitoring Web Site Design

The Nuclear Data Management and Analysis System (NDMAS) manages irradiation experiment data collected under the Advanced Gas Reactor (AGR) Fuel Development and Qualification program within the Advanced Reactor Technologies Technology Development Office. The AGR-5/6/7 irradiation experiment combines the fifth, sixth, and seventh planned irradiation campaigns of the U.S. Department of Energy AGR Fuel Development and Qualification Program. These combined irradiation tests will consist of fuel qualification tests (AGR-5/6) and a margin test (AGR-7) for the industrially produced uranium oxycarbide (UCO) tristructural isotropic (TRISO) coated particle fuel developed by the AGR program. The objective of the AGR-5/6/7 irradiation experiment is to establish the performance of UCO TRISO fuel fabricated using engineering-scale equipment in a production environment under and beyond normal operating conditions (PNL-5245). Experimental irradiation measurements for this experiment (i.e., thermocouple temperature, gas flow rate, fission product release rate, gross gamma count, and Advanced Test Reactor (ATR) operational parameters) are captured automatically to the NDMAS database. Data derived from numerical simulation or other mathematical analyses (i.e., fast fluence, burnup, temperature, and fission product release to birth ratio) are captured to the database when provided by the researchers. The NDMAS database is a relational database accessed via structured query language and managed with Microsoft SQL Server. While select users can directly access the database, that is not the most convenient way to interact with the data. The NDMAS team constructs numerous tables that combine related datasets, and delivers those data to researchers via graphs and spreadsheets on a Microsoft SharePoint-based website. For the AGR-5/6/7 experimental data, a new subsite has been developed, along with a set of web pages. These pages will be used by members of fuel irradiation team for monitoring irradiation conditions according to specification (SPC-1749), by the physics modelers to access necessary model inputs, and by the nuclear engineering community to view and access data such as fuel temperatures, fission product release from capsules, and ATR operational parameters. The deliverable represented in this document is a SharePoint website containing tables of the AGR-5/6/7 measured and calculated data, graphs displaying the data, and links to source documents and references.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

An SQL query generator for CLIPS

As expert systems become more widely used, their access to large amounts of external information becomes increasingly important. This information exists in several forms such as statistical, tabular data, knowledge gained by experts and large databases of information maintained by companies. Because many expert systems, including CLIPS, do not provide access to this external information, much of the usefulness of expert systems is left untapped. The scope of this paper is to describe a database extension for the CLIPS expert system shell. The current industry standard database language is SQL. Due to SQL standardization, large amounts of information stored on various computers, potentially at different locations, will be more easily accessible. Expert systems should be able to directly access these existing databases rather than requiring information to be re-entered into the expert system environment. The ORACLE relational database management system (RDBMS) was used to provide a database connection within the CLIPS environment. To facilitate relational database access a query generation system was developed as a CLIPS user function. The queries are entered in a CLlPS-like syntax and are passed to the query generator, which constructs and submits for execution, an SQL query to the ORACLE RDBMS. The query results are asserted as CLIPS facts. The query generator was developed primarily for use within the ICADS project (Intelligent Computer Aided Design System) currently being developed by the CAD Research Unit in the California Polytechnic State University (Cal Poly). In ICADS, there are several parallel or distributed expert systems accessing a common knowledge base of facts. Expert system has a narrow domain of interest and therefore needs only certain portions of the information. The query generator provides a common method of accessing this information and allows the expert system to specify what data is needed without specifying how to retrieve it.

Snyder, James↗

The CEBAF Element Database and Related Operational Software

The newly commissioned 12GeV CEBAF accelerator relies on a flexible, scalable and comprehensive database to define the accelerator. This database delivers the configuration for CEBAF operational tools, including hardware checkout, the downloadable optics model, control screens, and much more. The presentation will describe the flexible design of the CEBAF Element Database (CED), its features and assorted use case examples.

43 PARTICLE ACCELERATORS↗

TenSQL v.2023.01.20

SAND2024-02520O Tensor SQL Database performs certain relational database management system/structured query language (RDBMS/SQL) queries faster than is possible using existing state-of-the-art databases. Tensor SQL is optimized for sparse linear algebra problems and other whole-table queries. Currently, the database is being used only for research and program development. Sandia National Laboratories is a multimission laboratory managed and operated by National Technology & Engineering Solutions of Sandia, LLC, a wholly owned subsidiary of Honeywell International Inc., for the U.S. Department of Energy’s National Nuclear Security Administration under contract DE-NA0003525.

Roose, Jonathan↗

Second Line of Defense Master Spares Catalog

This catalog is intended to be a comprehensive listing of repair parts, components, kits, and consumable items used on the equipment deployed at SLD sites worldwide. The catalog covers detection, CAS, network, ancillary equipment, and tools. The catalog is backed by a Master Parts Database which is used to generate the standard report views of the catalog. The master parts database is a relational database containing a record for every part in the master parts catalog along with supporting tables for normalizing fields in the records. The database also includes supporting queries, database maintenance forms, and reports.

Henderson, Dale L.↗