The Experts below are selected from a list of 20061 Experts worldwide ranked by ideXlab platform
K. Dritz - One of the best experts on this subject based on the ideXlab platform.
-
System administrator's manual (SAM) for the enhanced logistics intratheater support tool (ELIST) Database Instance segment version 8.1.0.0 for solaris 7.
2002Co-Authors: K. DritzAbstract:This document is the System Administrator's Manual (SAM) for the Enhanced Logistics Intratheater Support Tool (ELIST) Database Instance Segment. It covers errors that can arise during the segment's installation and deinstallation, and it outlines appropriate recovery actions. It also tells how to change the password for the SYSTEM account of the Database Instance after the Instance is created, and it discusses the creation of a suitable Database Instance for ELIST by means other than the installation of the segment. The latter subject is covered in more depth than its introductory discussion in the Installation Procedures (IP) for the Enhanced Logistics Intratheater Support Tool (ELIST) Global Data Segment, Database Instance Segment, Database Fill Segment, Database Segment, Database Utility Segment, Software Segment, and Reference Data Segment (referred to in portions of this document as the ELIST IP). The information in this document is expected to be of use only rarely. Other than errors arising from the failure to follow instructions, difficulties are not expected to be encountered during the installation or deinstallation of the segment. By the same token, the need to create a Database Instance for ELIST by means other than the installation of the segment is expected to be the exception, rather than the rule. Most administrators will only need to be aware of the help that is provided in this document and will probably not actually need to read and make use of it.
-
Software version description (SVD) for the enhanced logistics intratheater support tool (ELIST) Database Instance segment version 8.1.0.0 for solaris 7.
2002Co-Authors: K. DritzAbstract:This document is the Software Version Description (SVD) for the Enhanced Logistics Intratheater Support Tool (ELIST) Database Instance Segment. It contains basic information about the segment.
-
Software test plan/description/report (STP/STD/STR) for the enhanced logistics intratheater support tool (ELIST) global data segment. Version 8.1.0.0, Database Instance Segment Version 8.1.0.0, ... [elided] and Reference Data Segment Version 8.1.0.0
2002Co-Authors: K. Dritz, M. Absil-mills, K. JacobsAbstract:This document is the Software Test Plan/Description/Report (STP/STD/STR) for the DII COE Enhanced Logistics Intratheater Support Tool (ELIST) mission application. It combines in one document the information normally presented separately in a Software Test Plan, a Software Test Description, and a Software Test Report; it also presents this information in one place for all the segments of the ELIST mission application. The primary purpose of this document is to show that ELIST has been tested by the developer and found, by that testing, to install, deinstall, and work properly. The information presented here is detailed enough to allow the reader to repeat the testing independently. The remainder of this document is organized as follows. Section 1.1 identifies the ELIST mission application. Section 2 is the list of all documents referenced in this document. Section 3, the Software Test Plan, outlines the testing methodology and scope--the latter by way of a concise summary of the tests performed. Section 4 presents detailed descriptions of the tests, along with the expected and observed results; that section therefore combines the information normally found in a Software Test Description and a Software Test Report. The remaining small sections present supplementary information. Throughout this document, the phrase ELIST IP refers to the Installation Procedures (IP) for the Enhanced Logistics Intratheater Support Tool (ELIST) Global Data Segment, Database Instance Segment, Database Fill Segment, Database Segment, Database Utility Segment, Software Segment, and Reference Data Segment.
-
software test plan description report stp std str for the enhanced logistics intratheater support tool elist global data segment version 8 1 0 0 Database Instance segment version 8 1 0 0 elided and reference data segment version 8 1 0 0 for solaris 7
Other Information: PBD: 6 Mar 2002, 2002Co-Authors: K. Dritz, M Absilmills, K. JacobsAbstract:This document is the Software Test Plan/Description/Report (STP/STD/STR) for the DII COE Enhanced Logistics Intratheater Support Tool (ELIST) mission application. It combines in one document the information normally presented separately in a Software Test Plan, a Software Test Description, and a Software Test Report; it also presents this information in one place for all the segments of the ELIST mission application. The primary purpose of this document is to show that ELIST has been tested by the developer and found, by that testing, to install, deinstall, and work properly. The information presented here is detailed enough to allow the reader to repeat the testing independently. The remainder of this document is organized as follows. Section 1.1 identifies the ELIST mission application. Section 2 is the list of all documents referenced in this document. Section 3, the Software Test Plan, outlines the testing methodology and scope--the latter by way of a concise summary of the tests performed. Section 4 presents detailed descriptions of the tests, along with the expected and observed results; that section therefore combines the information normally found in a Software Test Description and a Software Test Report. The remaining small sections present supplementary information. Throughout this document, the phrase ELIST IP refers to the Installation Procedures (IP) for the Enhanced Logistics Intratheater Support Tool (ELIST) Global Data Segment, Database Instance Segment, Database Fill Segment, Database Segment, Database Utility Segment, Software Segment, and Reference Data Segment.
K. Jacobs - One of the best experts on this subject based on the ideXlab platform.
-
Software test plan/description/report (STP/STD/STR) for the enhanced logistics intratheater support tool (ELIST) global data segment. Version 8.1.0.0, Database Instance Segment Version 8.1.0.0, ... [elided] and Reference Data Segment Version 8.1.0.0
2002Co-Authors: K. Dritz, M. Absil-mills, K. JacobsAbstract:This document is the Software Test Plan/Description/Report (STP/STD/STR) for the DII COE Enhanced Logistics Intratheater Support Tool (ELIST) mission application. It combines in one document the information normally presented separately in a Software Test Plan, a Software Test Description, and a Software Test Report; it also presents this information in one place for all the segments of the ELIST mission application. The primary purpose of this document is to show that ELIST has been tested by the developer and found, by that testing, to install, deinstall, and work properly. The information presented here is detailed enough to allow the reader to repeat the testing independently. The remainder of this document is organized as follows. Section 1.1 identifies the ELIST mission application. Section 2 is the list of all documents referenced in this document. Section 3, the Software Test Plan, outlines the testing methodology and scope--the latter by way of a concise summary of the tests performed. Section 4 presents detailed descriptions of the tests, along with the expected and observed results; that section therefore combines the information normally found in a Software Test Description and a Software Test Report. The remaining small sections present supplementary information. Throughout this document, the phrase ELIST IP refers to the Installation Procedures (IP) for the Enhanced Logistics Intratheater Support Tool (ELIST) Global Data Segment, Database Instance Segment, Database Fill Segment, Database Segment, Database Utility Segment, Software Segment, and Reference Data Segment.
-
software test plan description report stp std str for the enhanced logistics intratheater support tool elist global data segment version 8 1 0 0 Database Instance segment version 8 1 0 0 elided and reference data segment version 8 1 0 0 for solaris 7
Other Information: PBD: 6 Mar 2002, 2002Co-Authors: K. Dritz, M Absilmills, K. JacobsAbstract:This document is the Software Test Plan/Description/Report (STP/STD/STR) for the DII COE Enhanced Logistics Intratheater Support Tool (ELIST) mission application. It combines in one document the information normally presented separately in a Software Test Plan, a Software Test Description, and a Software Test Report; it also presents this information in one place for all the segments of the ELIST mission application. The primary purpose of this document is to show that ELIST has been tested by the developer and found, by that testing, to install, deinstall, and work properly. The information presented here is detailed enough to allow the reader to repeat the testing independently. The remainder of this document is organized as follows. Section 1.1 identifies the ELIST mission application. Section 2 is the list of all documents referenced in this document. Section 3, the Software Test Plan, outlines the testing methodology and scope--the latter by way of a concise summary of the tests performed. Section 4 presents detailed descriptions of the tests, along with the expected and observed results; that section therefore combines the information normally found in a Software Test Description and a Software Test Report. The remaining small sections present supplementary information. Throughout this document, the phrase ELIST IP refers to the Installation Procedures (IP) for the Enhanced Logistics Intratheater Support Tool (ELIST) Global Data Segment, Database Instance Segment, Database Fill Segment, Database Segment, Database Utility Segment, Software Segment, and Reference Data Segment.
Jun Yang - One of the best experts on this subject based on the ideXlab platform.
-
SIGMOD Conference - Explaining Wrong Queries Using Small Examples
Proceedings. ACM-Sigmod International Conference on Management of Data, 2019Co-Authors: Zhengjie Miao, Sudeepa Roy, Jun YangAbstract:For testing the correctness of SQL queries, a standard practice is to execute the query in question on some test Database Instance and compare its result with that of the correct query. Given two queries $Q_1$ and $Q_2$, we say that a Database Instance D is a counterexample (for $Q_1$ and $Q_2$) if $Q_1(D)$ differs from $Q_2(D)$; such a counterexample can serve as an explanation of why $Q_1$ and $Q_2$ are not equivalent. While the test Database Instance may serve as a counterexample, it may be too large or complex to understand where the inequivalence arises. Therefore, in this paper, given a known counterexample D for $Q_1$ and $Q_2$, we aim to find the smallest counterexample $D' \subseteq D$ where $Q_1(D') \neq Q_2(D')$. The problem in general is NP-hard. Drawing techniques from provenance and constraint solving, we develop a suite of algorithms for finding small counterexamples for different classes of queries, including those involving negation and aggregation. We evaluate the effectiveness and scalability of our algorithms on student queries from an undergraduate Database course, and on queries from the TPC-H benchmark. We also report a user study from the course where we deployed our tool to help students with an assignment on relational algebra.
-
SIGMOD Conference - RATest: Explaining Wrong Relational Queries Using Small Examples
Proceedings. ACM-Sigmod International Conference on Management of Data, 2019Co-Authors: Zhengjie Miao, Sudeepa Roy, Jun YangAbstract:We present a system called RATest, designed to help debug relational queries against reference queries and test Database Instances. In many applications, e.g., classroom learning and regression testing, we test the correctness of a user query Q by evaluating it over a test Database Instance D and comparing its result with that of evaluating a reference (correct) query $Q_0$ over D. If $Q(D)$ differs from $Q_0(D)$, the user knows Q is incorrect. However, D can be large (often by design), which makes debugging Q difficult. The key idea behind RATest is to show the user a much smaller Database Instance $D' \subseteq D$, which we call a counterexample, such that $Q(D') \neq Q_0(D')$. RATest builds on data provenance and constraint solving, and employs a suite of techniques to support, at interactive speed, complex queries involving differences and group-by aggregation. We demonstrate an application of RATest in learning: it has been used successfully by a large undergraduate Database course in a university to help students with a relational algebra assignment.
Yang Jin - One of the best experts on this subject based on the ideXlab platform.
-
The Techniques for Establishing ORACLE User Database Instance Based on Windows NT/98
2001Co-Authors: Yang JinAbstract:This paper introduces the installing of oracle 7 3 on Windows NT/98 and modifying of the config files,discusses the techniques for establishing oracle user Database Instance,gives out the example of how to connect the user Database
-
the techniques for establishing oracle user Database Instance based on windows nt 98
Sichuan University of Science and Technology, 2001Co-Authors: Yang JinAbstract:This paper introduces the installing of oracle 7 3 on Windows NT/98 and modifying of the config files,discusses the techniques for establishing oracle user Database Instance,gives out the example of how to connect the user Database
Jan Chomicki - One of the best experts on this subject based on the ideXlab platform.
-
SUM - Consistent Query Answering: The First Ten Years
Lecture Notes in Computer Science, 2008Co-Authors: Jan ChomickiAbstract:Usually, the data in a Database Instance is supposed to be consistentand satisfy the Database integrity constraints. However, it is quite common for the two to diverge. The data may fail to satisfy the constraints for various reasons: it may be erroneous, out of date, or come from mutually inconsistent sources.
-
Minimal-change integrity maintenance using tuple deletions
Information & Computation, 2005Co-Authors: Jan Chomicki, Jerzy MarcinkowskiAbstract:We address the problem of minimal-change integrity maintenance in the context of integrity constraints in relational Databases. We assume that integrity-restoration actions are limited to tuple deletions. We focus on two basic computational issues: repair checking (is a Database Instance a repair of a given Database?) and consistent query answers [in: ACM Symposium on Principles of Database Systems (PODS), 1999, 68] (is a tuple an answer to a given query in every repair of a given Database?). We study the computational complexity of both problems, delineating the boundary between the tractable and the intractable cases. We consider denial constraints, general functional and inclusion dependencies, as well as key and foreign key constraints. Our results shed light on the computational feasibility of minimal-change integrity maintenance. The tractable cases should lead to practical implementations. The intractability results highlight the inherent limitations of any integrity enforcement mechanism, e.g., triggers or referential constraint actions, as a way of performing minimal-change integrity maintenance.
-
Minimal-Change Integrity Maintenance Using Tuple Deletions
arXiv: Databases, 2002Co-Authors: Jan Chomicki, Jerzy MarcinkowskiAbstract:We address the problem of minimal-change integrity maintenance in the context of integrity constraints in relational Databases. We assume that integrity-restoration actions are limited to tuple deletions. We identify two basic computational issues: repair checking (is a Database Instance a repair of a given Database?) and consistent query answers (is a tuple an answer to a given query in every repair of a given Database?). We study the computational complexity of both problems, delineating the boundary between the tractable and the intractable. We consider denial constraints, general functional and inclusion dependencies, as well as key and foreign key constraints. Our results shed light on the computational feasibility of minimal-change integrity maintenance. The tractable cases should lead to practical implementations. The intractability results highlight the inherent limitations of any integrity enforcement mechanism, e.g., triggers or referential constraint actions, as a way of performing minimal-change integrity maintenance.
