Database Schema Change Interception and Registration System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database management systems lack efficient methods for managing schema changes, particularly in ensuring that schema change commands are properly registered, released, and recorded, leading to potential conflicts and data integrity issues.
Innovation Solution
A system and method that intercepts database commands, registers schema change commands meeting specific criteria, releases them for execution when conditions are met, and logs them in a history storage, ensuring controlled and tracked schema modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If schema change commands are directly executed without registration and control, then productivity is improved due to faster execution, but reliability deteriorates due to potential conflicts and data integrity issues
Solution Approach 1:
The system performs preliminary registration of schema change commands before execution. The registration process captures the command details, identifies affected objects, and stores metadata in a registration table. This preliminary action enables subsequent control operations (approval, rejection, rollback) without impacting the original execution speed, as the registration occurs in parallel to the execution workflow.
Solution Approach 2:
The patent introduces an intermediary control layer between schema change commands and their execution. This intermediary consists of registration tables and control procedures that mediate between the user's intent and the actual database modification. The intermediary enables reliability controls (conflict detection, approval workflows) while maintaining productivity through efficient query optimization and parallel processing capabilities.
2Reliability
If schema change commands are registered and controlled through a management system, then reliability is improved through conflict prevention and tracking, but device complexity increases due to additional registration and release mechanisms
Solution Approach 1:
The registration table structure is designed to be universal and multi-functional. It stores not only registration information but also execution status, approval state, and rollback capability in a single integrated structure. This multi-functionality reduces the need for separate tracking mechanisms, thereby reducing overall system complexity while maintaining comprehensive control over schema changes.
Solution Approach 2:
The system implements self-service capabilities where the registration process automatically captures necessary metadata, identifies conflicts, and manages execution states without requiring manual intervention for each schema change. The automatic conflict detection and release mechanisms operate autonomously based on predefined rules, reducing the operational complexity despite the increased structural complexity of the control system.
3Measurement precision
If all schema change commands are intercepted and registered, then measurement precision is improved for tracking changes, but loss of time occurs due to additional processing steps
Solution Approach 1:
The system applies partial action by selectively registering and controlling schema change commands based on predefined criteria. Not all commands require full registration and approval workflows - only those that meet specific conditions (affecting critical objects, making structural changes, etc.). This selective approach maintains high measurement precision for tracked changes while minimizing time loss by bypassing unnecessary processing steps for routine operations.
Data Source
AI summary
Methods, systems and program storage devices for managing schema changes made by a user to an object in a database. The method including: (a) intercepting a database command entered by said user; (b) if said database command is a schema change command referencing said object in said database and a registry criterion is met, then inserting said database command or a command derived therefrom into a registered storage, otherwise releasing said database command to said database for execution thereby; (c) releasing said database command or a command derived therefrom from said registered storage to said database for execution thereby when a release criterion is met thus giving rise to a released command; and (d) inserting said released command or a command derived therefrom into a history storage.