Business data migration using metadata

• US 7,509,327 B2
• Filed: 12/03/2003
• Issued: 03/24/2009
• Est. Priority Date: 12/03/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: LeQuere, Patrick R., Joshi, Nisheth P., Manek, Parul
• Primary Examiner(s): Truong; Cam Y T
• Application Number:
  US10/727,258
• Publication Number:
  US 20050125463A1
• Time in Patent Office: 1,938 Days
• Field of Search: 707/3, 707/10, 707200-205, 707/102
• US Class Current: 1/1
• CPC Class Codes: G06F 16/86 Mapping to a database
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: Y10S 707/99936 Pattern matching access
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Metadata driven business data migration is provided. An extensible business data destination system is provided having metadata that describes its structure. An intermediate database is structurally synchronized to the extensible destination system prior to receiving source data. Once the structural synchronization between the destination system and the intermediate database has been completed, the intermediate database is populated with source data. Customizable migration overhead information is stored and used to allow highly configurable specification of data migration. Once migration information has been specified, and any required manipulations have been completed with respect to the source data in the intermediate database, a migration tool generates business data in the destination system to complete the migration.

Claims

1. A method of migrating business data from a source system to an extensible destination system, the method comprising:

at a computer, examining a structural definition of the extensible destination system, wherein the examining the structural definition of the extensible destination system includes accessing metadata related to the extensible destination system;

synchronizing a structure of an intermediate database system with the extensible destination system, wherein the intermediate database system includes an entity extension table and an entity base table, the entity extension table and the entity base table are stored in a computer readable storage medium, wherein the synchronizing is performed prior to receiving source data, wherein the entity extension table is populated based upon an extension in the extensible destination system, the entity extension table exists only for destination extensible system entities that are customizable;

collecting the source data from the source system and populating the synchronized structure of intermediate database system with the source data;

specifying whether an attribute is used to define relationships between entities, whether the attribute should be migrated and migration status of the attribute;

setting how many records from the entities are to be imported into the destination system when a migration tool is executed;

specifying order in which the entities are migrated to preserve dependencies;

migrating the source data from the intermediate database system to the extensible destination system according to migration overhead information, the migrating follows the order specified in the attribute, wherein the migration overhead information includes user-configurable, and an EntityMigrationInfo table and wherein the EntityMigrationInfo table specifies information about migration for each entity to be migrated.

2. The method of claim 1, wherein synchronizing the structure of the intermediate database system with the extensible destination system includes invoking an initialization tool.

3. The method of claim 1, wherein the user-configuration is limited to using one or more predefined software procedures.

4. The method of claim 1, wherein migration overhead information includes information about which entities are to be migrated.

5. The method of claim 1, wherein migration overhead information includes information about how many entities will be migrated.

6. The method of claim 1, wherein migration overhead information includes information about which attributes will be migrated.

7. The method of claim 1, wherein the migration overhead information includes an EntityAttribute table.

8. The method of claim 1, wherein the migration overhead information is stored as part of an intermediate database.

9. The method of claim 1, wherein an intermediate database is embodied on a Structured Query Language (SQL) server.

10. A computer readable storage medium having stored instructions for migrating business data from a source system to an extensible destination system, wherein the instructions are executed by a computer for performing steps:

examining a structural definition of the extensible destination system, wherein the examining the structural definition of the extensible destination system includes accessing metadata related to the extensible destination system;

synchronizing a structure of an intermediate database system with the extensible destination system, wherein the intermediate database system includes an entity extension table and an entity base table, the entity extension table and the entity base table are stored in a memory, wherein the synchronizing is performed prior to receiving source data, wherein the entity extension table is populated based upon an extension in the extensible destination system, the entity extension table exists only for destination extensible system entities that are customizable;

collecting the source data from the source system and populating the synchronized structure of intermediate database system with the source data;

specifying whether an attribute is used to define relationships between entities, whether the attribute should be migrated and migration status of the attribute;

setting how many records from the entities are to be imported into the destination system when a migration tool is executed;

specifying order in which the entities are migrated to preserve dependencies;

migrating the source data from the intermediate database system to the extensible destination system according to migration overhead information, the migrating follows the order specified in the attribute, wherein the migration overhead information includes user-configurable, and an EntityMigrationInfo table and wherein the EntityMigrationInfo table specifies information about migration for each entity to be migrated.

11. The computer readable storage medium of claim 10, wherein user-configuration is limited to using one or more predefined software procedures.

12. The computer readable storage medium of claim 10, wherein migration overhead information includes information about how many entities will be migrated.

13. The computer readable storage medium of claim 10, wherein the migration overhead information includes an EntityAttribute table.

14. The computer readable storage medium of claim 10, wherein the migration overhead information is stored as part of an intermediate database.