Database Migration Metadata Copying for Synthetic Data Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database migration methods are time-consuming due to the lengthy process of copying data from an original server to a new server, affecting efficiency.
Innovation Solution
A method that involves copying metadata with identification information of synthetic data, receiving a service instruction, determining if synthetic data needs to be retrieved, and copying it based on the identification information, optionally including incremental data and setting a synchronization position in the log to manage data migration efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all data in the original server is copied to the new server before receiving service instructions, then data completeness is ensured, but migration time is excessively long
Solution Approach 1:
The patent applies preliminary action by copying only metadata and identification information of synthetic data before receiving service instructions. This allows the system to prepare essential data structures in advance while deferring the copying of actual synthetic data until it is needed, thus reducing preliminary migration time while ensuring data completeness when required.
Solution Approach 2:
The patent segments the data copying process into two distinct phases: first copying metadata and identification information, then copying actual synthetic data on-demand based on service instructions. This segmentation allows the system to separate essential structural data from bulk data transfer, reducing initial migration time while maintaining data completeness.
2Productivity
If synthetic data is copied on-demand based on service instructions, then migration efficiency is improved, but data completeness may be compromised
Solution Approach 1:
The patent implements feedback by continuously monitoring service instructions and using them to determine which synthetic data needs to be copied. The system receives service instructions, analyzes them to identify required synthetic data, and then copies only that specific data. This feedback loop ensures data completeness is maintained while optimizing migration efficiency through selective copying.
3Speed
If metadata including identification information of synthetic data is copied in advance, then data retrieval efficiency is improved, but storage requirements increase
Solution Approach 1:
The patent applies the copying principle by creating lightweight metadata copies that contain only identification information of synthetic data, rather than copying the actual synthetic data in advance. This metadata serves as a reference index that enables efficient data retrieval without requiring substantial additional storage space, thus improving retrieval efficiency while minimizing storage requirements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present specification discloses a database migration method, including: copying metadata from a first server of a database, the metadata including identification information of synthetic data; receiving a service instruction sent by a client after the copying the metadata from the first server of the database; determining, based on the service instruction, whether the synthetic data needs to be retrieved from the first server of the database; and in response to it is determined that the synthetic data needs to be retrieved from the first server of the database, copying the synthetic data from the first server of the database based on the identification information of the synthetic data. According to the present invention, the service instruction sent by the client is received in advance, and the synthetic data is copied from the first server of the database based on the identification information of the synthetic data, thereby reducing time taken for database migration.