Database Synchronization via Sister Transactions and Delta Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database migration processes face challenges in synchronizing data between two databases with different structures and architectures, leading to inconsistencies and inefficiencies, especially in large DP projects where real-time updates and complex changes are required, and the migration process can impact the quality and performance of the original database.
Innovation Solution
The implementation of 'sister transactions' which are identical software program modules that simulate the original transactions on the second database, allowing for step-by-step migration and transparent data synchronization, using the same source programs to maintain and update the first database platform, ensuring that changes are made available in real-time and minimizing communication bandwidth and costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is continuously synchronized from the first database to the second database in real-time, then data consistency between the two databases is improved, but communication bandwidth consumption and processing costs increase significantly
Solution Approach 1:
The patent extracts only the changes (delta data) from the first database rather than transmitting the entire dataset. The extraction unit identifies and extracts only modified data records, which are then transmitted to the second database. This significantly reduces communication bandwidth consumption while maintaining data consistency.
Solution Approach 2:
The system performs preliminary actions by maintaining a change log that records all modifications before they need to be synchronized. The extraction unit refers to this pre-recorded change information to identify what needs to be transmitted, avoiding the need for continuous full-data comparisons and reducing real-time processing overhead.
2Device complexity
If the database migration is carried out in a single step (big bang approach), then the migration process is simplified, but system downtime increases and operational continuity is disrupted
Solution Approach 1:
The patent segments the migration process into multiple phases: initial data load, change tracking, and incremental synchronization. Instead of a single big bang migration, the system first loads initial data, then continuously tracks and synchronizes changes in smaller increments, allowing the system to remain operational throughout the migration process.
Solution Approach 2:
The system dynamically adjusts the migration approach based on operational requirements. The dual database configuration allows flexible switching between databases, and the synchronization process can be adjusted in real-time based on data change rates and system performance, enabling continuous operation during migration.
3Ease of operation
If the physical structures and organizational forms of the first and second databases are made identical to enable direct change mapping, then change synchronization becomes simpler, but adaptability to different database platforms and optimization opportunities are reduced
Solution Approach 1:
The patent introduces an intermediary mapping layer that translates changes from the first database structure to the second database structure. The mapping unit converts data changes according to predefined mapping relationships between the two different database schemas, enabling synchronization between structurally different databases without requiring identical physical organizations.
Solution Approach 2:
The system changes the parameters of data representation by maintaining multiple views of the same data in different structural formats. The mapping relationships allow the same logical changes to be represented in different physical structures suitable for each database platform, optimizing for both simplicity and adaptability.
4Productivity
If multiple application programs access and change the databases concurrently, then system functionality and user productivity are improved, but ensuring data consistency and handling concurrent changes becomes more complex
Solution Approach 1:
The patent implements feedback mechanisms through change logs and confirmation protocols. When changes are made to either database, the system records these changes and uses feedback information to coordinate subsequent synchronization operations, ensuring that concurrent changes from multiple applications are properly managed and reflected consistently across both databases.
Data Source
AI summary
Computer-supported method for building and/or synchronising a second database from/with a first database, accesses by work units being carried out at least on the first database from at least one application workstation, to generate, change or delete contents of the database, with at least one first server to guide and maintain the first database, said server being connected to at least one application workstation, at least one second server to guide and maintain the second database, at least one data connection which connects the two servers, a software program component being provided by which, in the case of a transaction which is initiated from one application workstation on the first database, a sister transaction can be called up on the second database and vice versa—in which case, from the point of view of the application workstation, the sister transaction on the side of the second database behaves analogously to its counterpart on the side of the first database.