Database Replication Log Segmentation and Dynamic Strategy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database replication methods face challenges in efficiently replicating data changes between source and target database systems, particularly when dealing with differing access times of memory devices, which can lead to deadlock situations and performance bottlenecks.
Innovation Solution
A method that generates log files for data changes, stores them on a fast memory device, archives some on a slower device, and selects between incremental and bulk replication strategies based on pending data changes and access times to prevent deadlock situations and optimize performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If log files are stored on a fast memory device with short access time, then data replication speed is improved, but storage cost and device complexity increase
Solution Approach 1:
The patent divides the storage system into two segments: a first storage device with short access time for storing active log files, and a second storage device with long access time for archiving old log files. This segmentation allows the system to maintain fast data replication speed for active logs while reducing overall storage complexity and cost by moving archived logs to slower, cheaper storage.
2Reliability
If all log files are kept on the fast memory device, then data synchronization is maintained, but storage cost and access time for archived logs increase
Solution Approach 1:
The patent implements preliminary action by archiving old log files to the second storage device in advance, before they are needed for bulk replication. This allows the system to maintain fast access to active logs for real-time replication while preparing archived logs ahead of time for later bulk operations, thus maintaining data synchronization without permanently keeping all logs on fast storage.
3Reliability
If incremental replication is used for all pending data changes, then data synchrony is maintained, but productivity decreases due to repeated small operations
Solution Approach 1:
The patent implements dynamic replication strategy selection based on the number of pending data changes. When the number of pending changes is below a threshold, incremental replication is used to maintain data synchrony. When the number exceeds the threshold, bulk replication is used to improve productivity. This dynamic adaptation resolves the contradiction by choosing the appropriate replication mode based on current system state.
4Productivity
If bulk replication is used for all pending data changes, then productivity is improved, but data synchrony and reliability decrease
Solution Approach 1:
The patent changes the replication parameter (incremental vs. bulk) based on the number of pending data changes. By monitoring this parameter and comparing it against a threshold, the system dynamically switches between replication modes. This ensures that bulk replication (which improves productivity) is only used when appropriate, while incremental replication (which maintains data synchrony) is used when needed, thus resolving the contradiction through parameter-based adaptation.
5Productivity
If the system continuously monitors and switches between replication types, then replication efficiency is optimized, but system complexity increases
Solution Approach 1:
The patent implements a feedback mechanism where the system continuously monitors the number of pending data changes and uses this information to dynamically select the appropriate replication type. This feedback loop allows the system to automatically adapt to changing conditions and optimize replication efficiency without requiring complex manual intervention or overly sophisticated control logic.
Data Source
AI summary
Methods, computer program products, and/or systems are provided that perform the following operations: generating log files while performing data changes of a source database system table; storing the log files on a first memory device having a first access time; archiving a part of the log files from the first memory device on a second memory device having a second access time, the second access time being higher than the first access time; tracking a second number of pending data changes, the pending data changes being data changes of the records of data change of log files archived on the second memory device which are not yet replicated in a target database system table; selecting a type of data replication from a first type of data replication and a second type of data replication based on the second number; and replicating the data changes in the target database system table.