Database Schema Migration Handling Redundant States
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database schema migration often results in redundant and invalid records due to the removal of states from the schema, leading to data integrity issues and complex logistics in updating multiple geographic locations, with existing solutions failing to address the specific challenge of handling records in a redundant state effectively.
Innovation Solution
A method and apparatus for migrating records from a source database schema to a target schema by marking redundant states, identifying resultant states, and calculating valid migration paths, using an interim schema to facilitate the transition of records to a valid state in the target schema, allowing users to select and execute valid migration paths to ensure data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If schema changes are batched together and applied to schema items in one go, then the schema update process is more efficient, but it becomes difficult to identify the required manual changes to the database containing the schema items
Solution Approach 1:
The patent segments the schema update process into individual change components, allowing the system to present changes in a structured format that shows the cumulative effect of multiple schema changes. This segmentation enables administrators to understand the impact of each change while maintaining batch processing efficiency.
Solution Approach 2:
The system performs preliminary analysis of schema changes before applying them, generating a preview of the impact on database items. This preliminary action allows administrators to see what manual changes will be required before committing to the batch update, reducing the complexity of identifying changes later.
2Duration of action of stationary object
If schema changes span many months or years, then comprehensive schema evolution is achieved, but it becomes difficult to identify the required manual changes to the database
Solution Approach 1:
The patent divides long-term schema evolution into discrete, manageable change sets that can be analyzed individually. Each schema change is broken down into specific impacts on database items, making it feasible to track and understand changes even when they span months or years.
Solution Approach 2:
The system provides feedback mechanisms that show the cumulative impact of schema changes over time. Administrators can review how multiple changes interact and affect database items, enabling informed decisions about manual changes required even in long-evolution scenarios.
3Device complexity
If schema migration is attempted without handling redundant states, then the migration process is simpler, but records in the database will exist in a redundant and thus invalid state causing exceptions
Solution Approach 1:
The patent applies preliminary actions to identify and handle records in redundant states before the schema migration is executed. The system pre-processes the database to flag, migrate, or archive records that would otherwise cause exceptions, ensuring data integrity while keeping the main migration process relatively simple.
Solution Approach 2:
The system takes preliminary anti-action by preventing records from entering invalid states during migration. It proactively identifies potential data integrity issues and applies corrective measures before they can cause migration failures, thus maintaining reliability without significantly complicating the migration process.
4Adaptability or versatility
If local system administrators must understand schema changes to apply them at multiple geographic locations, then customization and local control are enabled, but lengthy outages and complex logistics are required to bring all databases up to the required level
Solution Approach 1:
The patent enables preliminary preparation of schema changes and migration scripts that can be distributed to multiple geographic locations. Administrators can review and customize changes locally in advance, then apply them simultaneously or in a coordinated sequence, reducing overall outage duration while maintaining local control.
Solution Approach 2:
The system provides universal schema change templates and migration frameworks that work across multiple geographic locations. While allowing local customization, the core migration logic and tools are standardized, enabling efficient coordinated updates across distributed databases without requiring entirely separate processes at each location.
Data Source
AI summary
There is disclosed a method, apparatus and computer program for migrating records in a database from a source database schema to a target database schema. A request is received to delete a state from the source schema. The state is marked as the redundant state. A resultant state is identified to which to migrate database records in the redundant state and a valid migration path is calculated between the redundant state and the resultant state.