Linking of parent-child data records in a legacy software modernization system

• US 8,639,675 B2
• Filed: 08/28/2008
• Issued: 01/28/2014
• Est. Priority Date: 08/28/2008
• Status: Active Grant

• Current Assignee: NTT DATA Canada, Inc. (Nippon Telegraph and Telephone Corporation)
• Original Assignee: MAKE Technologies, Inc. (Dell Technologies Inc.)
• Inventors: Cotichini, Christian, White, Michael E. F., Green, David John
• Primary Examiner(s): BROWN, SHEREE N
• Application Number:
  US12/200,617
• Publication Number:
  US 20100057759A1
• Time in Patent Office: 1,979 Days
• Field of Search: 707/602, 707/696
• US Class Current: 707/696
• CPC Class Codes: G06F 16/2272 Management thereof
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

A system and method for linking parent and child data records during data migration is disclosed. One embodiment comprises sequentially receiving a plurality of data records from an arbitrary source of records without running a query on the source of records, generating a destination store of records that contains the plurality of data records, and locating any records in the destination store of records that has a dangling key. In this way, the embodiment may correct dangling keys to generate a destination store of records with referential integrity.

Claims

1. A method comprising:

at a conversion engine executed on a computing device;

sequentially loading a plurality of legacy data records from a legacy source data file stored in an arbitrary source without running a query on the arbitrary source, the plurality of legacy data records including parent records and child records;

concurrently migrating the parent records and corresponding child records while loading additional legacy data records, wherein the parent records and corresponding child records are migrated, independently and in parallel, through a data migration workbench transformer of the conversion engine, such that during the loading of the plurality of data records;

one or more of the parent data records are uploaded and assigned corresponding surrogate keys, and the respective child data records linked to each of the one or more parent data records are assigned corresponding foreign keys, and such that one or more other child data records are uploaded and assigned corresponding surrogate keys, and the respective parent data records linked to the other child data records are assigned corresponding foreign keys;

generating a destination store of records that contains the migrated parent records and child records;

locating at least one record in the destination store of records that has a dangling key;

correcting dangling keys to generate a destination store of records with referential integrity, wherein correcting dangling keys includes at least one of deleting the record with the dangling key or changing the dangling key in the record to create a valid foreign key, where the destination store of records is configured as a low-level representation of a physical data layout of a target database.

2. The method of claim 1, further comprising logging the records with dangling keys prior to correcting the dangling keys.

3. The method of claim 2, further comprising generating a report containing the logged records.

4. The method of claim 1, wherein the arbitrary source is a database.

5. The method of claim 1, wherein the arbitrary source is a flat file.

6. The method of claim 1, wherein the arbitrary source is a network stream.

7. A non-transitory computer-readable medium comprising computer-executable instructions being executable by a modernization system to:

at a conversion engine executed on a computing device;

sequentially load a plurality of legacy data records from a legacy source data file stored in an arbitrary source without running a query on the arbitrary source, the plurality of legacy data records including parent records and child records;

concurrently migrate the parent records and corresponding child records while loading additional legacy data records, wherein the parent records and corresponding child records are migrated, independently and in parallel, through a data migration workbench transformer of the conversion engine, such that during the loading of the plurality of records;

one or more of the parent data records are uploaded and assigned corresponding surrogate keys, and the respective child data records linked to each of the one or more parent data records are assigned corresponding foreign keys, and such that one or more other child data records are uploaded and assigned corresponding surrogate keys, and the respective parent data records linked to the other child data records are assigned corresponding foreign keys;

generate a destination store of records that contains the migrated parent records and child records;

locate at least one record in the destination store of records that has a dangling key; and

correct dangling keys to generate a destination store of records with referential integrity, wherein correcting dangling keys includes at least one of deleting the record with the dangling key or changing the dangling key in the record to create a valid foreign key, where the destination store of records is configured as a low-level representation of a physical data layout of a target database.

8. The non-transitory computer-readable medium of claim 7, further comprising instructions executable to log the records with dangling keys prior to correcting the dangling keys.

9. The non-transitory computer-readable medium of claim 8, further comprising instructions executable to generate a report containing the logged records.

10. The non-transitory computer-readable medium of claim 7, wherein the arbitrary source is a database.

11. The non-transitory computer-readable medium of claim 7, wherein the arbitrary source is a flat file.

12. The non-transitory computer-readable medium of claim 7, wherein the arbitrary source is a network stream.