Automated Configuration Table Versioning with Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional relational database tables lack automated versioning and rollback capabilities, making it difficult to manage and revert large-scale enterprise processes effectively.
Innovation Solution
The implementation of a system that includes a processor and memory to retrieve and extend database tables with versioning, using instead-of triggers to simulate a versioned database, increment version numbers, and enable automated rollback by managing data block versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If conventional relational database tables are used, then the database structure is simple and easy to implement, but automated versioning and rollback capabilities are not supported
Solution Approach 1:
The patent creates a copy of the database table structure by introducing a versioned view layer. Instead of modifying the base table directly, a new view is created that copies the table structure and adds versioning capabilities. This allows automated versioning without changing the original simple table structure.
Solution Approach 2:
The patent segments the database into base tables and versioned views. The base tables maintain their simple structure while the versioned views handle the versioning logic. This segmentation allows the simple base tables to remain unchanged while gaining automated versioning capabilities through the view layer.
2Extent of automation
If conventional relational database tables are used, then the database structure is simple, but rollback of large blocks of transaction is not automatically supported
Solution Approach 1:
The patent performs preliminary action by creating versioned views before transactions occur. The view maintains historical versions of data, so when rollback is needed, the system can immediately retrieve previous versions from the view without complex manual intervention. This preliminary setup enables automated rollback capability.
Solution Approach 2:
The versioned view creates a copy of the base table structure that includes historical data. This copy serves as a backup that can be restored during rollback operations, enabling automated rollback of large transaction blocks without modifying the original simple table structure.
3Extent of automation
If versioning is implemented in conventional database tables, then automated versioning is achieved, but the database structure becomes complex
Solution Approach 1:
The patent segments versioning functionality into a separate view layer rather than embedding it in the base table structure. This segmentation keeps the base tables simple while adding versioning capabilities at the view level, thus avoiding structural complexity in the core table definitions.
Solution Approach 2:
The versioned view acts as an intermediary between the simple base table and the versioning requirements. It mediates between the simple structure of base tables and the complex needs of versioning, providing automated versioning capabilities without directly modifying the base table structure.
4Ease of operation
If large blocks of data are rolled back manually, then rollback can be performed, but the process is difficult and time-consuming
Solution Approach 1:
The system performs preliminary action by maintaining historical versions in the view before rollback is needed. When rollback is required, the system can immediately query and restore previous versions from the view, eliminating the need for manual, time-consuming rollback processes.
Solution Approach 2:
The versioned view enables self-service rollback by automatically providing the ability to restore previous states. The system serves itself by using the pre-created versioned data to perform rollback operations without requiring manual intervention or complex rollback procedures.
Data Source
AI summary
Arrangements for automated versioning of configuration tables with the ability of automated rollback are provided. A database table having key fields and data fields may be retrieved. The table may be extended by adding a new key field to each row of the database table. The new key field may include a version number and a data block identifier. A view of the table may be generated and initialized by setting a current version number to zero. One or more triggering components for simulating a versioned database may be defined. The one or more triggering components may include one or more instead-of triggers used to insert, update, or delete from the database table upon an insert, update, or delete operation on the view. The versioned database may be simulated using the one or more triggering components, including an instead-of-insert trigger, an instead-of-update trigger, and/or an instead-of-delete trigger.