Selective Database Migration via Snapshot Fragmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database migration across different DBMS and environments is challenging due to compatibility issues, requiring custom code and lacking versatility, especially when migrating to different database vendors or cluster layouts, and often necessitates full replication which is not always necessary or feasible.
Innovation Solution
The method involves creating a snapshot of a source database with selective record inclusion and fragmentation, using a hierarchical file system, and deserializing it into a target database with filters, allowing partial replication and supporting different DBMS and operating systems, enabling flexible migration and testing without overwriting the production system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full database replication is performed, then migration completeness is improved, but resource consumption and migration time increase
Solution Approach 1:
The patent extracts only the necessary subset of data from the source database based on user-defined criteria (e.g., specific tables, rows matching certain conditions, or data from particular clusters). This selective extraction approach reduces resource consumption while maintaining migration completeness for the intended purpose, as opposed to replicating the entire database.
Solution Approach 2:
The database migration process is segmented into discrete, manageable units (snapshots) that can be selectively created and transferred. Each snapshot represents a portion of the database that can be independently managed, transferred, and restored, enabling partial replication that balances completeness with resource efficiency.
2Manufacturing precision
If custom migration code is written for each database pair, then migration precision is improved, but device complexity and development time increase
Solution Approach 1:
The patent implements a universal migration framework that can handle multiple database types and configurations through a single standardized platform. The system uses configurable snapshots and selection criteria that work across different database vendors and cluster layouts, eliminating the need for custom migration code for each database pair while maintaining migration precision through flexible filtering and selection mechanisms.
3Adaptability or versatility
If database migration is performed to different DBMS and environments, then adaptability is improved, but compatibility issues and migration difficulty increase
Solution Approach 1:
The patent introduces a standardized intermediate representation (snapshot) that acts as a mediator between source and target databases. This snapshot format serves as a universal intermediary that can be generated from various source DBMS and transformed into different target DBMS, abstracting away the compatibility complexities and enabling flexible migration across different database vendors and environments without direct complex interactions between source and target systems.
4Productivity
If selective record migration is implemented, then migration speed and resource usage are improved, but data consistency and selection accuracy challenges increase
Solution Approach 1:
The patent performs preliminary action by allowing users to define selection criteria and fragmentation parameters before the actual migration occurs. The system pre-processes these criteria to create a plan for selective record extraction, ensuring accurate and consistent selection during migration. This preliminary configuration enables high-speed selective migration while maintaining data consistency through pre-established selection rules.
Data Source
AI summary
Selective migration of a database in which one or more computing devices establish a creation specification for a snapshot of a subset of a source database of a source database management system (DBMS). The device(s) receive instruction to create the snapshot in accordance with the creation specification. The device(s) retrieve, in response to receiving the instruction to create, record(s) from the source database in accordance with the creation specification. The device communicates, via broadcast, the retrieved records to one or more creation listeners; and serializes, by each listener and in accordance with the creation specification, the broadcast records into the snapshot comprising the fragments and the parts.