Database Conversion System with Intermediary Mediator

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Converting databases from one data model to another is a time-consuming and error-prone process, requiring significant manual work and resulting in potential service breaks and data inconsistencies, especially when migrating large databases to different database management systems.

Innovation Solution

A method and system for converting source objects from one data model to another by generating target objects with identifying information, merging data collections, and updating changes, allowing for the coexistence of databases with different data models and reducing service breaks during conversion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional data conversion methods are used to migrate databases between different DBMS, then data can be transferred between incompatible systems, but the process is time-consuming and error-prone requiring multiple iterations

Engineering Contradiction:

Improveconversion accuracyVSAvoidconversion time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically generating conversion specifications and executing test conversions before the final conversion. This includes validating the conversion process, identifying errors early, and preparing the target database structure in advance, thereby reducing the time and errors in the actual data migration process

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary conversion management system that coordinates between source and target databases. This intermediary automatically handles the mapping between different data models, manages conversion specifications, and orchestrates test and final conversions, eliminating the need for manual intervention and reducing conversion time while maintaining accuracy

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If manual conversion specifications are designed and custom applications are written, then data mapping between different data models can be achieved, but the process requires significant manual work and is time-consuming

Engineering Contradiction:

Improvedata model compatibilityVSAvoidconversion efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The system enables self-service by automatically generating conversion specifications based on the source and target data models. The conversion management system autonomously identifies mapping relationships, creates conversion rules, and executes conversions without requiring manual specification design or custom application development, thereby significantly improving productivity while maintaining adaptability to different data models

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system provides universality through a generic conversion management framework that can handle conversions between any different data models and DBMS. The system is not limited to specific database systems but can adapt to various source and target configurations, making it a versatile tool that improves productivity across different conversion scenarios without requiring model-specific customizations

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Reliability

If the source database is changed during conversion, then data can be updated to reflect current state, but the target database becomes outdated and requires re-conversion

Engineering Contradiction:

Improvedata consistencyVSAvoidconversion time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system ensures continuity by enabling the source database to remain operational and accept changes during the conversion process. The conversion management system continuously monitors the source database for changes and can perform incremental updates to the target database, ensuring data consistency is maintained throughout the conversion without requiring the source database to be taken offline or frozen

Inventive Principle:

Principle #20Continuity of useful action

Solution Approach 2:

The system introduces dynamics by making the conversion process adaptive to changes in the source database. Rather than a static one-time conversion, the system can detect changes in the source database and dynamically update the conversion process, either by re-executing conversions for changed data or by applying change data capture techniques to keep the target database synchronized with the source

Inventive Principle:

Principle #15Dynamics

4Reliability

If test conversions are carried out before real conversion, then errors can be detected and corrected, but multiple iterations are required before acceptable results are achieved

Engineering Contradiction:

Improveconversion qualityVSAvoidconversion throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system implements feedback by automatically analyzing the results of test conversions and using this information to improve subsequent conversions. The conversion management system captures error patterns, validates conversion rules, and adjusts conversion specifications based on test results, thereby reducing the number of iterations needed while maintaining high conversion quality and reliability

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS10776313B2Converting source objects to target objects

Publication Date: 2020.09.15 TEKLA

AI summary

Source objects according to a source data model are converted to target objects according to a target data model. A plurality of target data collections are generated, each including uniquely identifiable target objects. A first generated target data collection is merged with a subsequently generated target data collection.