Database Consistency Checks via Quality System Test Conditions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Determining whether foreign key relationships in a database will be appropriate in a production system is time-consuming and resource-intensive due to the complexity of database systems, and existing methods often require transmitting entire table records for consistency checks, which wastes resources and affects system performance.
Innovation Solution
A method that performs consistency checks by generating test conditions at the quality database system to verify if updated records in a constrained table have corresponding values in a second table, without sending unnecessary data to the production system, allowing updates to be applied only after ensuring consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If entire table records are transmitted from quality system to production system for consistency checks, then data consistency can be verified, but network traffic increases and system performance is affected
Solution Approach 1:
The patent extracts only the essential test conditions (foreign key relationships and constraints) from the complete table records. Instead of transmitting entire tables, the system generates and transmits only the minimal set of test conditions required to verify consistency, thereby reducing network traffic while maintaining verification capability.
Solution Approach 2:
The consistency check process is segmented into two phases: (1) generating test conditions at the quality system based on foreign key relationships, and (2) executing only those specific test conditions at the production system. This segmentation allows verification without transmitting complete table data.
2Reliability
If entire table records are transmitted for consistency checks, then data consistency can be verified, but resource consumption increases
Solution Approach 1:
The system extracts and transmits only the essential test conditions (foreign key relationships and constraints) from the complete table records. Instead of transmitting entire tables, the system generates and transmits only the minimal set of test conditions required to verify consistency, thereby reducing network traffic while maintaining verification capability.
3Measurement precision
If consistency checks are performed at production system with complete data, then accuracy is improved, but system performance is degraded
Solution Approach 1:
The patent applies partial action by executing only the specific test conditions related to foreign key relationships and constraints, rather than performing comprehensive validation on all table data. This selective approach maintains accuracy for critical consistency checks while minimizing performance impact on the production system.
Solution Approach 2:
Test conditions are generated in advance at the quality system based on the database schema and foreign key relationships. This preliminary generation of test conditions allows the production system to execute only targeted checks rather than processing complete table data, thereby maintaining accuracy while improving performance.
Data Source
AI summary
Techniques and solutions are described for determining whether an update to be sent to a production database system from a quality database system will provide consistent table relationships if applied at the production database system. These consistency checks can be carried out without transmitting entire table records from the quality system to the production system, which can reduce network traffic. These consistency checks can also reduce performance impacts at the production system, as test condition generation can be carried out at the quality database system. A consistency check method can include the quality database system determining values of updated or added records of a first table that should be consistent with a second table. The test conditions cause the production database system to execute a test to determine whether the values are present in the production system. Consistency violations can be remedied before the update is applied.