Trigger-Based Database Modification Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data extraction techniques for tracking database modifications in high-availability systems are resource-intensive, time-consuming, and prone to inaccuracies, leading to data inconsistency, especially when dealing with frequent reference data changes in production environments.
Innovation Solution
A trigger-based system that identifies input tables, generates triggers, and tracks database modifications, storing information associated with these changes for subsequent packaging and deployment across multiple systems, ensuring data consistency and minimal downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If full data dump or pre-defined rules are used for data extraction, then data changes can be tracked, but resource consumption and time increase significantly
Solution Approach 1:
The patent extracts only the specific information related to data changes from the database using triggers, rather than performing full data dumps. The trigger-based mechanism captures only modified records, their types, and relevant metadata, significantly reducing the amount of data processed and stored while maintaining complete tracking accuracy.
Solution Approach 2:
The patent implements triggers in advance on the database tables before data modification operations occur. These pre-configured triggers automatically capture change information as it happens, eliminating the need for post-processing or periodic full scans of the database, thereby reducing both time and computational resources.
2Reliability
If full data dump or pre-defined rules are used for data extraction, then data changes can be tracked, but the process becomes time-consuming
Solution Approach 1:
The patent extracts only the specific information related to data changes from the database using triggers, rather than performing full data dumps. The trigger-based mechanism captures only modified records, their types, and relevant metadata, significantly reducing the amount of data processed and stored while maintaining complete tracking accuracy.
Solution Approach 2:
The patent implements triggers that continuously and automatically capture data changes as they occur in real-time. This continuous monitoring mechanism ensures no changes are missed while eliminating periodic processing delays, maintaining data consistency without time-consuming batch operations.
3Productivity
If conventional extraction techniques are used, then data can be collected, but inaccuracies and data inconsistency occur
Solution Approach 1:
The patent implements triggers that provide immediate feedback when data changes occur. The trigger mechanism validates and captures change information at the source, ensuring accuracy by detecting modifications as they happen rather than relying on periodic scans or external monitoring that may miss or misinterpret changes.
Solution Approach 2:
The database tables themselves perform the tracking function through self-contained triggers embedded within them. Each table monitors its own modifications autonomously, eliminating reliance on external extraction processes that may introduce errors or inconsistencies in data collection.
Data Source
AI summary
An apparatus, computer program, and method are provided for trigger-based tracking of database modifications. One or more input tables associated with a database are identified. Further, one or mom triggers are generated, based on the one or more input tables. Such one or more triggers are then installed in connection with an application configured for modifying the database. In response to at least one of the one or more triggers being triggered, one or more modifications to the database are tracked. Further, information is stored where such information is associated with the one or more modifications to the database.