Database Zero Downtime Upgrade via Table Links and Triggers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database upgrades often require downtime, as existing methods necessitate creating backups and duplicating data, leading to increased memory consumption and inefficiencies.
Innovation Solution
The implementation of table links and application triggers allows for concurrent access and data replication between different database versions, enabling zero-downtime upgrades by creating clones of tables and using calculated fields, which minimizes memory usage and persists data efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional database upgrade methods are used, then data consistency is ensured, but system downtime increases and memory consumption increases
Solution Approach 1:
The patent segments the database schema into multiple versions (first access schema and second access schema) that can coexist. Table link objects allow different application versions to access different schema versions simultaneously, enabling parallel operation without requiring full system downtime for upgrades.
Solution Approach 2:
The patent introduces table link objects as intermediaries between application versions and database tables. These link objects act as mediators that enable concurrent access to the same underlying data by different application versions with different access schemas, resolving the conflict between maintaining data consistency and enabling zero-downtime upgrades.
2Productivity
If table clones are created for upgrade, then data replication is enabled, but memory consumption increases
Solution Approach 1:
The patent uses table link objects that reference existing database tables rather than creating full physical clones. The link objects establish virtual connections to the same underlying data storage, allowing multiple application versions to access and replicate data from the same source without duplicating the actual data in memory.
Solution Approach 2:
The table link objects serve multiple functions simultaneously: they enable concurrent access for different application versions, support data replication through triggers, and maintain referential integrity. This multi-functionality eliminates the need for separate dedicated structures for each purpose, reducing overall memory consumption.
3Adaptability or versatility
If multiple access schemas are maintained, then concurrent access is enabled, but device complexity increases
Solution Approach 1:
The table link objects serve as intermediaries that abstract the complexity of managing multiple access schemas. They provide a unified interface for accessing tables while handling the underlying schema versioning and compatibility logic, reducing the apparent complexity for applications while enabling concurrent access to different schema versions.
Solution Approach 2:
The patent implements application triggers that automatically execute when data changes occur through table link objects. This feedback mechanism ensures data consistency and coordination between different access schemas without requiring complex manual management, as the system automatically responds to changes and maintains integrity across versions.
Data Source
AI summary
An upgrade of a first version of a database application to a second version of a database application that both have a same data schema is initiated. The first database application has a first access schema such that at least one table in the data schema is linked to the first access schema. The second version of the database application has a second access schema such that at least one table in the data schema is linked to the second access schema. Subsequently, concurrent access is provided for each access schema to at least one database table in the data schema to the first and second versions of the database application. The concurrent access is enabled by a respective at least one table link object in each of the first access schema and the second access schema that is used by database views or stored procedures such access schema.