Database Catalog Signatures for Targeted, Lower-Downtime Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional database system upgrades involve full rebuilds regardless of structural or content changes, leading to time-consuming and disruptive processes.
Innovation Solution
A deployment system generates catalog shape and content signatures to determine changes between versions, selecting from full, minor, or binary swap upgrades based on these signatures to optimize the upgrade process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full rebuild upgrade process is used, then the database system is upgraded to the new version, but the upgrade time and system downtime increase significantly
Solution Approach 1:
The patent segments the upgrade process into multiple types (full rebuild, partial rebuild, zero-downtime upgrade) based on the detected changes in database catalog structure and content. By dividing the monolithic upgrade approach into granular strategies, the system only performs necessary rebuild operations on affected components rather than the entire database catalog, thereby reducing upgrade time and downtime while maintaining upgrade completeness.
Solution Approach 2:
The patent performs preliminary actions by generating and comparing catalog signatures (structure signatures and content signatures) before executing the upgrade. This preliminary analysis identifies whether changes exist and what type of changes occurred, allowing the system to pre-determine the appropriate upgrade strategy and avoid unnecessary full rebuilds, thus reducing upgrade time.
2Reliability
If conventional full rebuild upgrades are performed, then all database catalog changes are handled, but unnecessary rebuilds increase processing overhead and resource consumption
Solution Approach 1:
The patent applies partial action by performing only the necessary portion of the rebuild operation based on detected changes. Instead of always executing a complete full rebuild, the system performs partial rebuilds on only those catalog components that have structure or content changes, eliminating unnecessary processing overhead and resource consumption while maintaining complete handling of all actual changes.
Solution Approach 2:
The patent implements feedback by comparing catalog signatures from the old version with signatures from the new version to detect changes. This feedback mechanism informs the upgrade process selection, allowing the system to adjust its actions based on actual change detection results, thereby improving processing efficiency by avoiding redundant full rebuilds while ensuring all necessary changes are handled.
3Reliability
If the database catalog structure or content changes between versions, then an upgrade is necessary, but determining the appropriate upgrade type adds complexity to the upgrade process
Solution Approach 1:
The patent introduces catalog signatures (structure signatures and content signatures) as intermediaries to detect and communicate changes between database catalog versions. These signatures act as mediators that simplify the complexity by providing a clear indication of what has changed, allowing the system to automatically determine the appropriate upgrade type without complex manual analysis, thus maintaining upgrade appropriateness while managing process complexity.
Solution Approach 2:
The patent uses parameter changes in catalog signatures (structure signatures and content signatures) to determine the appropriate upgrade type. By monitoring changes in these specific parameters, the system can automatically select between full rebuild, partial rebuild, or zero-downtime upgrade strategies, making the complex upgrade process determination systematic and automated based on detectable parameter differences.
Data Source
AI summary
Techniques are disclosed that pertain to upgrading a database application. A computer system may determine to upgrade a database application from a current version associated with a first instance of a database catalog that defines the structure of a database that is managed by that database application. The first instance is associated with a first catalog signature that is indicative of the first instance of the database catalog. The computer system generates a second catalog signature that is indicative of a second instance of the database catalog that is associated with the different version. The computer system compares the first catalog signature and the second catalog signature to determine whether the database catalog changes between the current and different versions. Based on the comparing, the computer system then selects one of multiple upgrade processes performable to upgrade the database application to the different version and performs the selected upgrade process.