Database Migration GUI for Schema Mapping and Script Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual generation of scripts for migrating data from a source database to a destination database is a time-consuming process, often taking several months or years, especially for complex applications, due to the need for manual understanding and scripting of both schemas.

Innovation Solution

A graphical user interface (GUI) is used to display and modify mappings between entities of the source and destination databases, allowing users to visualize and define how data is to be migrated, with the system generating scripts based on these mappings for automated data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual script generation is used for database migration, then migration accuracy and control are improved, but migration time and effort increase significantly

Engineering Contradiction:
Improvemigration accuracyVSAvoidmigration time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs self-service by automatically generating migration scripts through AI/ML algorithms that analyze source and destination schemas, identify mappings, and produce executable scripts without requiring manual intervention for each mapping decision, thus reducing migration time while maintaining accuracy through automated intelligence

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

An AI/ML-based intermediary system is introduced between the source and destination databases to automatically analyze schemas, determine mappings, and generate migration scripts. This intermediary handles the complex mapping decisions that would otherwise require manual expertise, reducing both time and maintaining precision

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If automated script generation is used for database migration, then migration speed is improved, but control and customization capability deteriorate

Engineering Contradiction:
Improvemigration speedVSAvoidcontrol capability
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system transitions from static manual control to dynamic adaptive control where the AI/ML model automatically adjusts mapping decisions based on schema analysis, but allows users to intervene and modify decisions when needed. This dynamic approach maintains speed while restoring control capability through selective human-in-the-loop validation

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where automated script generation is followed by validation steps that allow users to review and modify mappings. The AI model can also learn from feedback to improve future automated decisions, balancing speed with control through iterative refinement

Inventive Principle:
Principle #23Feedback

3Measurement precision

If comprehensive manual mapping is performed for all database entities, then mapping precision is improved, but complexity of the process increases

Engineering Contradiction:
Improvemapping precisionVSAvoidprocess complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The complex mapping process is segmented into automated AI-driven steps (schema analysis, entity identification, mapping suggestion) and manual review steps. This segmentation reduces overall process complexity by handling routine precision-critical tasks automatically while reserving manual effort for exception handling and validation

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10616337B1Graphical user interface (GUI) that facilitates database migration
Publication Date: 2020.04.07 HARRIS DAWN HLDG INC
  • US10616337B1 patent drawing
  • US10616337B1 patent drawing
  • US10616337B1 patent drawing

AI summary

Described herein are features pertaining to displaying a graphical user interface (GUI) that depicts mappings between entities of a source database and entities of a destination database. A database migrator is able to interact with the GUI to approve preliminary mappings as well as to modify preliminary mappings. Once the database migrator approves the mappings, scripts can be generated, wherein the scripts are usable to migrate data from the source database to the destination database.