Data Summarization Pause Mechanism for RDBMS MDBMS Sync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing summarization programs face complexity and unavailability issues when handling large volumes of data across different technologies like RDBMS and MDBMS, particularly in managing the state of summarization data and ensuring high availability, leading to difficulties in predicting when summarization can be run and synchronizing data post-availability.
Innovation Solution
Implementing a pause mechanism that allows summarization to be paused and resumed based on request, with a pause identifier and exclusive lock management, and utilizing a quarantine for data processing to ensure data integrity and availability, even when one technology is unavailable.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data transformations are broken into multiple steps to handle large volumes of data, then the summarization process becomes more manageable and recoverable, but the complexity of tracking data state increases
Solution Approach 1:
The patent introduces a pause identifier mechanism that is established before the summarization process begins. This preliminary action allows the system to pre-define evaluation points and lock management strategies, enabling state tracking without adding operational complexity during the actual summarization execution.
Solution Approach 2:
The patent employs an exclusive lock mechanism as an intermediary between the multi-step transformation process and the data state tracking system. This lock acts as a mediator that simplifies state management by providing a clear binary state (locked/unlocked) that indicates whether data is being modified, thereby reducing the complexity of tracking data across multiple transformation steps.
2Loss of information
If the summarization program is closely integrated with the source system to extract actively transacting data, then the data extracted is more relevant and current, but the system becomes unavailable when summarization runs
Solution Approach 1:
The patent implements a dynamic pause mechanism that allows the summarization process to be temporarily suspended based on evaluation needs. The pause identifier can be set or cleared dynamically, enabling the system to switch between extraction mode and evaluation mode as needed, thus maintaining both data relevance and system availability through flexible state transitions.
Solution Approach 2:
The patent introduces periodic evaluation points through the pause mechanism, where the summarization process periodically stops to allow data evaluation. This periodic action ensures that data is evaluated at appropriate intervals without requiring continuous system unavailability, balancing data currency with system availability by creating structured pauses rather than continuous interruptions.
3Manufacturing precision
If the summarization program waits for MDBMS availability to ensure data synchronization, then data integrity is maintained, but the summarization program cannot continue when MDBMS is unavailable
Solution Approach 1:
The patent establishes pause identifiers and lock mechanisms as preliminary structures that define evaluation points before summarization begins. These pre-defined structures allow the system to proceed with summarization using RDBMS data when MDBMS is unavailable, while still maintaining the capability to synchronize later when MDBMS becomes available, thus ensuring both data integrity and program continuity.
Solution Approach 2:
The patent segments the summarization process into distinct phases marked by pause identifiers: an extraction phase that can proceed independently using RDBMS data, and a synchronization phase that occurs when MDBMS is available. This segmentation allows the summarization program to continue productivity in the extraction phase while maintaining data synchronization accuracy in the synchronization phase, resolving the contradiction between continuity and precision.
Data Source
AI summary
Embodiments of the invention provide systems and methods for providing summarizations of data and transactions based on the status of the summarization and the data and transactions being summarized. According to one embodiment, a method for providing summarizations of data and transactions related to one or more applications can comprise initiating a first summarization of the data and transactions related to the one or more applications. The first summarization can be paused in response to a request to evaluate the data and transactions being summarized. Data and transactions available for summarization can be evaluated in response to and based on the request. The first summarization can be resumed upon a completion or a timeout of the evaluating of the data and transactions being summarized.