Schema Migration Metadata Change Detection via File Hashing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Database schema migrations are computationally expensive due to the need for synchronizing design time and runtime metadata, with current methods relying on costly database queries to compare and update metadata, which can be slow and inefficient.

Innovation Solution

A method that uses file hashes to quickly detect changes in design time metadata without querying runtime metadata, allowing for reduced database queries by comparing hashes to determine if changes have occurred, and only querying the database when changes are detected to synchronize runtime objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If database queries are performed to compare design time metadata with runtime metadata during schema migration, then synchronization accuracy is improved, but computational expense and time consumption increase

Engineering Contradiction:

Improvesynchronization accuracyVSAvoidmigration time

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

The system generates and stores hash values of design time metadata files before migration occurs. During schema migration, these pre-computed hash values are retrieved and compared with hash values of runtime metadata, eliminating the need for expensive database queries to fetch and compare actual metadata content. This preliminary action of hashing resolves the contradiction by enabling fast comparison that maintains synchronization accuracy.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent replaces the mechanical/database query-based metadata comparison system with a hash-based comparison system. Instead of querying the database to retrieve and compare runtime metadata with design time metadata, the system substitutes this with a lightweight hash computation and comparison operation, dramatically reducing computational expense and migration time while preserving synchronization accuracy.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If database queries are performed to retrieve runtime metadata for comparison, then metadata synchronization is ensured, but computational expense increases

Engineering Contradiction:

Improvemetadata synchronizationVSAvoidcomputational expense

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system substitutes expensive database query operations with lightweight hash file system operations. Instead of querying the database to retrieve runtime metadata for comparison, the system retrieves pre-stored hash values from the file system and compares them, ensuring metadata synchronization reliability while dramatically reducing computational expense and energy consumption.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent creates hash copies of metadata files and stores them in a migration metadata table. These hash copies serve as lightweight representations that can be quickly retrieved and compared without accessing the actual metadata or querying the database, thus ensuring synchronization reliability while minimizing computational expense.

Inventive Principle:

Principle #26Copying

3Manufacturing precision

If full metadata comparison is performed during every schema migration, then synchronization accuracy is maintained, but productivity decreases

Engineering Contradiction:

Improvesynchronization accuracyVSAvoidmigration speed

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The system performs preliminary hash computation of design time metadata files and stores these hash values in a migration metadata table before migration occurs. During schema migration, only hash value comparisons are performed rather than full metadata comparisons, maintaining synchronization accuracy while dramatically improving migration speed and productivity.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Instead of performing complete metadata comparison during every schema migration, the system performs only the essential hash value comparison, which is a partial action that suffices to detect changes. This partial comparison approach maintains synchronization accuracy for the critical aspects while significantly improving migration productivity.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS20250021533A1High speed database schema change detection

Publication Date: 2025.01.16 SAP IRELAND LTD

AI summary

Embodiments describe a technique for database schema migration that minimizes queries to the runtime database. A technique is described for detecting whether design time metadata has changed during a schema migration without performing a database query for runtime metadata and comparing the design time metadata with the runtime metadata. The technique may improve performance since it aims at minimizing the number of times the database is queried for runtime metadata during the schema migration.