Heterogeneous Database Materialized View Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Heterogeneous databases face challenges in synchronizing query results efficiently due to compatibility issues, leading to performance problems when trying to refresh materialized views across remotely located and incompatible database servers.
Innovation Solution
A method for synchronizing query results between heterogeneous databases involves determining synchronization needs, generating and transmitting synchronization commands between database servers, and performing fast refresh operations to ensure consistent materialized view updates without requiring direct interpretation of metadata by the second database server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If materialized view synchronization is performed between heterogeneous databases, then query result consistency is improved, but system complexity increases due to compatibility issues
Solution Approach 1:
The patent introduces a synchronization command as an intermediary mechanism that enables data transfer between heterogeneous databases without requiring the second database server to interpret the first database's metadata formats. The synchronization command acts as a universal interface that translates and standardizes data exchange, resolving compatibility issues while maintaining query result consistency across different database systems.
Solution Approach 2:
The patent segments the synchronization process into distinct components: metadata generation at the source database, synchronization command creation, and command execution at the target database. This segmentation allows each component to operate independently with standardized interfaces, reducing system complexity while ensuring reliability through modular error handling and validation at each stage.
2Measurement precision
If direct metadata interpretation is performed by the second database server, then synchronization accuracy is improved, but processing time increases
Solution Approach 1:
The patent applies preliminary action by pre-generating synchronization commands at the first database server before data transfer. The metadata is processed and transformed into standardized synchronization commands in advance, eliminating the need for the second database server to perform complex metadata interpretation during the actual synchronization process. This reduces processing time while maintaining synchronization accuracy through pre-validation of data formats.
3Reliability
If materialized view refresh is performed frequently, then data freshness is improved, but performance overhead increases
Solution Approach 1:
The patent implements periodic action through scheduled synchronization operations that refresh materialized views at predetermined intervals. Instead of continuous or on-demand synchronization that would create performance overhead, the system performs refresh operations periodically according to a schedule, balancing data freshness requirements with system performance. The synchronization command mechanism enables efficient periodic execution with minimal impact on overall database performance.
Data Source
AI summary
According to an exemplary embodiment of the present invention, disclosed is a method for synchronizing query results between databases executed in a first database server. The method may include: determining synchronization of a materialized view present in a second database server which is remotely located from the first database server in which the materialized view refers to a master table present in the first database server and the first database server and the second database server are heterogeneous; generating a synchronization command to be transmitted to the second database server in response to determination of synchronization; and transmitting the generated synchronization command to the second database server to allow the second database server to synchronize the materialized view present in the second database server and the master table present in the first database server.