Dynamic Object-Relationship Model for Database Migration Sequencing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database migration often results in data integrity issues due to inaccurate object-relationship models, particularly when custom objects and attributes are not properly accounted for, leading to incomplete or missing data during schema changes.
Innovation Solution
A database migration system that builds a dynamic object-relationship model based on the current database schema, classifying object attributes into self-related, direct cross-related, indirect cross-related, and parent-child relationships to determine a precise migration sequence, thereby preserving data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a standard database schema is used for migration, then migration speed is improved, but data integrity deteriorates due to loss of custom attributes
Solution Approach 1:
The system performs preliminary actions by building a dynamic object-relationship model of the current customized database schema before migration. This model captures all custom objects, attributes, and relationships, which are then used to guide the migration process to ensure data integrity while maintaining efficiency
Solution Approach 2:
The system creates a copy of the current database schema structure through the dynamic object-relationship model, which replicates the customized schema including all non-standard attributes and relationships. This copied model serves as a template for accurate migration without requiring trial and error
2Loss of information
If custom attributes are migrated without proper sequencing, then completeness is improved, but migration complexity increases due to relationship dependencies
Solution Approach 1:
The system employs a dynamic object-relationship model that adapts to the specific customized schema being migrated. The model dynamically determines the migration sequence based on actual database relationships rather than following a fixed complex procedure, simplifying the migration process while ensuring completeness
Solution Approach 2:
The system replaces manual trial-and-error migration approaches with an automated mechanism that uses the dynamic object-relationship model to determine migration sequences. This substitution eliminates the need for complex manual intervention while ensuring all custom attributes and relationships are properly migrated
Data Source
AI summary
A database migration system, according to an example of the present disclosure, builds a dynamic object-relationship model of a database and determines a sequence of data migration for moving data from one database to another. The system may determine a dynamic object-relationship model based on a traversal of the database schema from a root object. The system may determine object attributes for child objects in the object database. In an example, an object attribute may be a relationship between the object and another object, or a property of the object. The system may build a dynamic object-relationship model based on the determined object attributes. The system may also determine a sequence for migrating the objects in the database that does not result in missing objects or missing object attributes based on the dynamic object-relationship model.