Automated Data Migration Model Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data migration between computer systems is often lengthy and inefficient due to the need for extensive analysis and development, as the understanding of data structures and relationships typically resides with individual analysts, leading to duplication of effort and ineffectiveness of previously developed scripts and programs when system changes occur.
Innovation Solution
A system comprising a migration modeler that monitors data migration operations to generate a migration model, which is then used by a migration automation manager to create a data migration program for subsequent migrations, leveraging captured data migration activity, system logs, and source code analysis to automate the process and iteratively refine the model.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual analysis and program development is performed for each data migration project, then data migration can be completed with customised analysis, but the process is lengthy and involves duplication of effort across different projects
Solution Approach 1:
The system performs preliminary monitoring of data migration operations to capture data transactions, system logs, and source code. This preliminary action creates a migration model that can be reused for future migrations, eliminating the need to repeat analysis and development work for each new project.
Solution Approach 2:
The system creates a reusable migration model that captures the essence of data migration operations. This model serves as a template that can be copied and applied to subsequent migration projects, reducing the need for manual analysis and program development while maintaining effectiveness.
2Loss of information
If data migration understanding resides in individual analysts' minds, then customised analysis can be performed, but the knowledge cannot be effectively transferred to other projects and duplication of effort occurs
Solution Approach 1:
The system automatically captures and documents migration knowledge through monitoring data transactions, system logs, and source code. This self-service approach eliminates the need for manual knowledge documentation and ensures that migration understanding is systematically captured and made available for future projects.
Solution Approach 2:
The system uses feedback from monitored migration operations to continuously refine and update the migration model. This feedback mechanism ensures that the captured knowledge remains accurate and relevant, improving both knowledge transfer efficiency and overall migration project efficiency.
3Adaptability or versatility
If customised programs are developed for each migration project, then specific data structure relationships can be addressed, but previously developed scripts become ineffective when system changes occur
Solution Approach 1:
The migration model is designed to be dynamic and adaptable. By continuously monitoring new migration operations and incorporating feedback from system logs and source code changes, the model automatically adjusts to system changes, maintaining effectiveness without requiring complete program redevelopment.
4Measurement precision
If manual analysis is performed for each migration project, then accurate data structure understanding can be achieved, but the process is lengthy and expensive
Solution Approach 1:
The system replaces manual mechanical analysis with automated electronic monitoring and analysis. By capturing data transactions, system logs, and source code electronically, the system achieves accurate data structure understanding much faster than manual analysis while reducing costs.
Data Source
AI summary
Technologies are provided for capturing information during a data migration and to use the captured information to generate data migration artefacts that can be used in subsequent data migrations. Artificial intelligence techniques can be used to analyze the captured data migration information and to generate a data migration model that can be used to create the data migration artefacts. Changes made to the data migration artefacts can be tracked and used to train the data migration model. Additionally or alternatively, during execution of the subsequent data migration, additional data migration information can be captured and used to train the data migration model. The captured data migration activity can include data access operations such as data transactions, system log activity, and/or source code for one or more data migration programs and/or scripts. Computer system version information can be detected and different migration artefacts can be created for different computer system versions.


