Database Schema Validation via Record Differencing and Whitelisting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database schema upgrades often result in differences between the upgraded and reference schemas, which can severely impact the functionality, performance, and usability of system management servers, as existing validation methods fail to effectively verify these changes.

Innovation Solution

A data differencing tool, specifically an upgrade controller, is used to compare the contents of reference and upgraded database schemas on a record-by-record basis, employing a whitelist to reduce false positives and focus on meaningful differences, ensuring accurate validation of schema upgrades.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a data differencing tool is used to compare database schemas on a record-by-record basis, then validation accuracy is improved, but computational complexity and processing time increase

Engineering Contradiction:
Improvevalidation accuracyVSAvoidcomputational complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The database schema validation is divided into multiple comparison passes: first comparing table structures and schemas at a high level, then performing record-by-record comparison only on specific tables or columns that are suspected to have changed. This segmentation allows detailed validation where needed while avoiding unnecessary computational overhead on unchanged portions of the database.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs a complete record-by-record comparison on critical tables that are most likely to contain meaningful changes, while using sampling or summary comparisons on less critical tables. This partial application of the most thorough comparison method balances validation accuracy with computational feasibility.

Inventive Principle:
Principle #16Partial or excessive action

2Difficulty of detecting and measuring

If comprehensive schema comparison is performed, then detection capability is improved, but false positives increase

Engineering Contradiction:
Improvedetection capabilityVSAvoidfalse positives
Core Design Contradiction:
Difficulty of detecting and measuringVSLoss of information

Solution Approach 1:

Different comparison strategies are applied to different parts of the database schema based on their importance and change likelihood. Critical tables with business logic receive full record-by-record comparison with strict validation, while metadata tables or configuration tables use more lenient comparison methods. This local differentiation reduces false positives by matching the detection strictness to the actual importance of each database component.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

Before performing detailed record comparisons, the system first compares table structures, column definitions, and schema metadata to identify potential differences. Only tables or columns that show structural differences or are flagged as high-priority undergo record-by-record comparison. This preliminary filtering prevents false positives by avoiding detailed comparison of tables that are structurally identical.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If detailed record-by-record comparison is performed, then validation thoroughness is improved, but processing time increases

Engineering Contradiction:
Improvevalidation thoroughnessVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The schema validation is performed in periodic stages: an initial quick validation checks table counts and basic structure, followed by targeted detailed comparisons of specific tables, and finally optional deep record-by-record comparison only for critical tables. This periodic approach with varying levels of detail allows the system to maintain validation thoroughness for important data while controlling overall processing time through staged execution.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS8266180B2Validation of database schema upgrades using a data differencing tool
Publication Date: 2012.09.11 RED HAT INC
  • US8266180B2 patent drawing
  • US8266180B2 patent drawing
  • US8266180B2 patent drawing

AI summary

An upgrade controller that compares the contents of a reference database with an upgraded database is described. In one embodiment, the upgrade controller connects to the reference and upgraded database and retrieves the list of tables. For each of the tables, the upgrade controller compares the content of the reference and the upgraded table. The upgrade controller compares the table contents by comparing the contents on a record-by-record basis. In addition, the upgrade controller can use a whitelist of tables and columns to reduce the number of false positive(s) that could be generated during the comparison.