Database Schema Update via Metadata Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database update methods, such as migration and incremental updates, face limitations due to the complexity of schema modifications and data dependencies, leading to inaccuracies over time.

Innovation Solution

A method that combines incremental updates with the migration approach by comparing metadata from the existing database and the update to generate a new schema, integrating new data into the database, allowing for accurate and efficient schema creation and data integration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the migration approach is used to update a database, then a completely new schema can be created, but the process requires developing entirely new schema and SQL migration scripts for every revision

Engineering Contradiction:
Improveschema accuracyVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary comparison of metadata between the existing database and the new version before executing the update. By analyzing schema differences in advance and generating appropriate migration scripts automatically, the system prepares the update path beforehand, reducing the actual update time while maintaining accuracy through comprehensive metadata analysis

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system copies and reuses existing metadata from the current database schema that remains unchanged in the new version. Instead of creating entirely new schema definitions, it identifies and replicates compatible metadata elements, significantly reducing the effort and time required for each migration while preserving schema accuracy

Inventive Principle:
Principle #26Copying

2Loss of time

If the incremental update approach is used to modify the database, then update time may be reduced, but schema modifications become impractical due to data dependencies

Engineering Contradiction:
Improveupdate timeVSAvoidschema modification ease
Core Design Contradiction:
Loss of timeVSEase of manufacture

Solution Approach 1:

The system introduces metadata comparison as an intermediary layer between the existing schema and the update process. This intermediary analyzes dependencies, identifies safe modification points, and generates targeted migration scripts that handle complex data relationships automatically, making schema modifications practical and manageable despite their complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system replaces manual schema modification processes with automated metadata comparison and script generation mechanisms. By using algorithmic analysis of metadata differences and automatic generation of migration scripts, the system eliminates the impracticality of manual schema updates while maintaining accuracy in handling data dependencies

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If frequent updates are performed using the migration approach, then the database can stay current, but new schema and scripts must be designed for every revision

Engineering Contradiction:
Improvedata accuracyVSAvoidschema management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically comparing metadata, identifying changes, and generating migration scripts without requiring manual intervention for each revision. This automation maintains data accuracy through consistent metadata analysis while dramatically reducing the complexity of managing frequent schema updates

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system creates a universal metadata comparison framework that handles multiple types of schema changes (tables, columns, constraints, relationships) through a single integrated process. This multi-functional approach maintains data accuracy across diverse update scenarios while simplifying the management complexity by providing a unified update mechanism

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7610298B2Difference-based database upgrade
Publication Date: 2009.10.27 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7610298B2 patent drawing
  • US7610298B2 patent drawing
  • US7610298B2 patent drawing

AI summary

A method for updating a database that combines the advantages of both the migration and incremental approach may resolve some of the problems associated with earlier methods. This may be accomplished by a methodology which incrementally updates new data while using the migration approach to create an entirely new schema. Such a method might compare the metadata from both the existing database and the data update to generate a new schema and integrate new data into the database.