Database Trigger Migration Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is a need for a reliable method to determine the success of migrating business-critical mainframe applications to open systems and cloud environments, as existing methods lack effectiveness in verifying the execution and data consistency post-migration.
Innovation Solution
A system and method that utilizes database triggers on both mainframe and open platforms to capture and compare database modification events, ensuring that the same data operations are performed on both platforms, thereby determining the success of the application migration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional migration verification methods are used, then the migration process is simple, but the reliability of determining migration success is insufficient
Solution Approach 1:
The patent introduces database triggers as intermediary components that automatically capture and record database modification events. These triggers act as mediators between the application execution and the verification process, automatically logging all data modifications without requiring complex manual verification procedures. This intermediary mechanism enables reliable migration success determination while keeping the verification system relatively simple.
Solution Approach 2:
The patent implements a feedback mechanism where database triggers continuously monitor and capture modification events, then compare these events between source and target systems. The comparison results provide feedback on migration success, enabling automated verification. This feedback loop ensures high reliability in migration success determination without requiring complex manual intervention.
2Measurement precision
If manual verification methods are used, then the verification process is simple to implement, but the measurement precision of data consistency is insufficient
Solution Approach 1:
The patent applies preliminary action by setting up database triggers in advance on both source and target databases before migration execution. These triggers are pre-configured to automatically capture modification events, so when migration occurs, the verification data is already recorded and ready for immediate comparison. This eliminates the need for time-consuming post-migration data sampling and achieves high measurement precision without time loss.
Solution Approach 2:
The database triggers perform self-service by automatically capturing, recording, and storing modification events without requiring external verification tools or manual intervention. The triggers themselves generate the verification data needed for precision measurement, enabling both high measurement precision and time efficiency simultaneously.
3Measurement precision
If comprehensive data comparison is performed, then the measurement precision of migration success is improved, but the loss of time for verification increases
Solution Approach 1:
The patent extracts only the essential verification information - database modification events - from the complex data set using triggers. Instead of comparing entire databases or large data sets, the triggers capture only the specific modification events (inserts, updates, deletes) that need to be verified. This extraction approach achieves high measurement precision by focusing on critical data while minimizing verification time by avoiding unnecessary data comparison.
Data Source
AI summary
In accordance with an embodiment, described herein is a system and method for determining the migration success of an application (e.g., a batch application) from a second computing platform (e.g., a mainframe platform) to a first computing platform (e.g., an open platform). A first database associated with the first computing platform and a second database associated with the second computing platform can include the same data baseline. A set of triggers can be created on each database to capture database modification events generated by the execution of a job associated with the application on each computing platform, and to store the database modification events in a table in each database. The database modification events from each computing platform can be downloaded and compared to determine the success of the application migration.