Database Structure Copying via Catalog Backup

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Relational database management systems require significant computing resources and time to generate SQL statements for copying or transitioning databases, often locking the database during the process and taking several hours.

Innovation Solution

The proposed solution involves exporting and recreating the database structure using catalog tables, preserving user table structures while modifying system-level tables to match the target database, thereby reducing the need for extensive computing resources and time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If traditional SQL statement generation method is used to copy or transition databases, then database structure can be copied accurately, but significant computing resources and time are required, and the database is locked during the process

Engineering Contradiction:

Improvedatabase structure accuracyVSAvoiddatabase copying speed

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The patent uses catalog export functionality to create a backup copy of the source database catalog, then modifies this copy to generate the target database structure. This avoids the need to generate complex SQL statements from scratch, significantly reducing computing resources and time while maintaining structural accuracy

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by exporting the catalog to a backup file before making any modifications. This pre-prepared catalog copy serves as a template that can be efficiently transformed into the target structure, avoiding time-consuming SQL generation during the actual database transition

Inventive Principle:

Principle #10Preliminary action

2Reliability

If traditional SQL statement generation method is used to copy or transition databases, then complete database transition is achieved, but the database remains locked for several hours

Engineering Contradiction:

Improvedatabase transition completenessVSAvoiddatabase locking duration

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the necessary catalog information from the source database into a separate backup file, then performs all modifications on this extracted copy. This separation allows the source database to remain unlocked and accessible, while the target database is built from the extracted catalog data without requiring prolonged locks

Inventive Principle:

Principle #2Taking out (Extraction)

3Adaptability or versatility

If traditional SQL statement generation method is used, then database version transition is accomplished, but extensive computing resources are consumed

Engineering Contradiction:

Improvedatabase version compatibilityVSAvoidcomputing resource consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

Instead of generating SQL statements that require extensive computing resources to process, the system copies the catalog structure to a backup file and performs modifications there. This copying approach maintains version compatibility through structural replication while consuming minimal computing resources

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent creates a temporary backup catalog file that serves as an intermediate working copy. This disposable copy allows all complex modifications to be performed efficiently, then the results are applied to the target database, avoiding the need for expensive and resource-intensive SQL generation and execution

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

Data Source

PatentUS11275725B2Transporting a database structure from a first version to a second version

Publication Date: 2022.03.15 SALESFORCE INC

AI summary

Methods and systems are provided for copying one database to another, such as where a database is upgraded from an earlier version to a later version. Database catalog files are used to copy the database table definitions, with appropriate changes made as needed between the first and second databases or database versions.