Quarantine Table for Database Constraint Violations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During maintenance procedures like upgrades, existing data in database systems often violates new constraints, leading to incomplete maintenance processes and prolonged downtime, as existing solutions are inefficient and not mass operation-/cloud-ready.
Innovation Solution
Implementing quarantine tables to temporarily hold and edit data values that violate constraints, allowing the system to be brought back online for production use after maintenance, thereby minimizing downtime and efficiently addressing constraint changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing data is cleaned to satisfy new constraints before maintenance, then constraint compliance is improved, but maintenance time and system downtime increase
Solution Approach 1:
The patent segments the data table into two parts: a quarantine table for storing non-compliant data and the main table for compliant data. This allows the maintenance procedure to complete constraint changes on the main table without being blocked by problematic data, while the quarantine table handles the non-compliant records separately.
Solution Approach 2:
The patent extracts non-compliant data records from the main table and moves them to a quarantine table. This extraction removes the blocking factor (non-compliant data) from the critical path of the maintenance procedure, allowing constraint changes to proceed without waiting for data cleaning.
2Manufacturing precision
If manual data cleaning is performed during maintenance, then data quality is improved, but operational costs and downtime increase
Solution Approach 1:
The patent implements automatic identification and movement of non-compliant data records using the deploy tool. The system self-services by automatically detecting which records violate the new constraints and moving them to the quarantine table without requiring manual intervention, thereby maintaining data quality while preserving operational efficiency.
Solution Approach 2:
The patent performs preliminary identification of non-compliant data before the maintenance procedure completes. By pre-identifying and quarantining problematic records, the system prepares the data state in advance, allowing the maintenance to proceed without delays for manual data cleaning during the actual maintenance window.
3Adaptability or versatility
If maintenance procedure completes with constraint changes, then system adaptability is improved, but data integrity may be compromised
Solution Approach 1:
The patent introduces a quarantine table as an intermediary structure between the main data table and the constraint enforcement mechanism. This intermediary holds non-compliant records that would otherwise block constraint implementation, allowing the system to adapt to new constraints while preserving data integrity by maintaining the non-compliant records in a controlled, isolated environment rather than deleting or corrupting them.
Data Source
AI summary
Methods, systems, and computer-readable storage media for determining at least one constraint that is to be changed as a result of a maintenance procedure that is to be performed on an application that interacts with a database system, identifying a data value of a table stored in the database as violating the at least one constraint, the table having a start release structure, moving a data object including the data value to a quarantine table that include the start release structure, editing the data value within the quarantine table to provide an edited data value that does not violate the at least one constraint, and moving the data object including the edited data value to the table, after the maintenance procedure has been performed.