Method of migrating legacy database systems
AssigneeFrontline Systems, Inc.
InventorDavid Tucker
Life of this patent
Estimating the term…
Abstract
A system and method for migrating legacy database systems to modern database comprises generally of the steps of gathering design information about the legacy database system; analyzing the metadata, data fields, and processes of the legacy system; iteratively creating business objects to represent the migrated data; iteratively associating each of the fields of the legacy database system to one or more of the business objects; creating a data migration script to effect the migration of data; and resolving inconsistencies between the legacy database systems and the one or more target database systems.
Claims20
A method of migrating one or more legacy database systems to one or more target database systems, the method comprising:
- gathering design information about the legacy database system, the design information including metadata, fields, relationships, and schema;
- analyzing existing metadata, data fields, and processes;
- creating business objects for the one or more target database, the business objects comprising attributes;
- associating one or more of the fields of the legacy database system to one or more of the business objects;
- creating a data migration script, the script executable by a computer to transfer data from the chosen fields of the legacy database systems to the one or more target database systems;
- executing the data migration script;
- and
- resolving inconsistencies between the legacy database systems and the one or more target database systems.
A method of migrating one or more legacy database systems to one or more target database systems, the method comprising:
- gathering system documentation for the legacy database system to capture terminology and identify associations between system processes and business processes;
- associating the legacy database systems with the gathered system documentation;
- identifying a multiplicity of actors involved in the legacy business process, the actors including users, customers, and outside computer systems;
- creating business objects for the one or more target database systems, the business objects comprising one or more attributes, the attributes having a data type;
- associating one or more of the fields of the legacy database system to one or more of the business objects;
- identifying fields in the legacy database system which will not be migrated to any of the one or more target database systems;
- creating a data migration script, the script executable by a computer to transfer data from the fields of the legacy database systems to the one or more target database systems;
- copying values in the replication database system to the attributes of the business objects of the one or more target database systems;
- and
- determining if errors or inconsistencies were introduced into the one or more target database systems during the copying step.
The method of claim 16 wherein after the step of identifying fields in the legacy database system that will not be migrated is the step of ensuring that each field in the legacy database system is either attributed to an attribute in one or more business objects or identified as not being migrated.
A method of migrating one or more legacy database systems to one or more target database systems, the method comprising::
- gathering system documentation for the legacy database systems to capture terminology and identify associations between system processes and business processes;
- retrieving schema information about one or more databases in the legacy database system;
- storing the schema information for the one or more legacy databases in a metadata database;
- saving connection parameters for each of the one or more legacy databases;
- associating each of the one or more legacy databases with the gathered system documentation;
- identifying a multiplicity of actors involved in the legacy business process, the actors including users, customers, and outside computer systems;
- identifying associations between the multiplicity of actors and one or more business functions of the legacy database system;
- identifying functional relationships between fields of the one or more legacy databases using one of legacy proximity, semantic similarity, and distributional similarity;
- creating business objects for the one or more target database systems, the business objects comprising attributes, the attributes having a data type;
- determining by functional dependency into which one or more of the business objects each of the one or more fields of the legacy database system should be migrated;
- attributing one or more fields of the legacy database system with one or more attributes of the one or more determined business objects;
- reviewing current mappings of legacy database fields to business object attributes to locate undocumented mappings;
- identifying zero or more fields in the legacy database system which will not be migrated to any of the one or more target database systems;
- ensuring that each field in the legacy database system is either attributed to an attribute in one or more business objects or identified as not being migrated;
- creating a data migration script, the script executable by a computer to transfer data from the fields of the legacy database systems to the one or more target database systems;
- copying the legacy database systems into a replication database system;
- copying values in the replication database system to the attributes of the business objects of the one or more target database systems;
- determining if errors or inconsistencies were introduced into the one or more target database systems during the copying step;
- storing located errors or inconsistencies in an exception database;
- and
- resolving the errors or inconsistencies stored in the exception database.
Dependencies are inferred from the claim text.