Method and system for a generic metadata-based mechanism to migrate relational data between databases

• US 7,620,665 B1
• Filed: 11/21/2000
• Issued: 11/17/2009
• Est. Priority Date: 11/21/2000
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Krychniak, Piotr, George, Joseph Mulavelil
• Primary Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US09/717,818
• Time in Patent Office: 3,283 Days
• Field of Search: 707/204, 707/200, 707/100, 707/101, 707/201, 707/202, 707/205, 707/203, 711/161, 711/162, 711/154
• US Class Current: 1/1
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A method and system for migrating data between databases is provided. Metadata is obtained from a source database and used to determine the manner in which the data within the source database should be migrated to a target database. The metadata provides a mechanism for structuring queries to retrieve the data within the source database in a generic manner, thereby providing a generic determination of the structure of the data to be migrated. The dependencies among tables in the source database are discovered, thereby providing an order to the migration operations to be performed when migrating the data. This order ensures that the data can be migrated correctly in the presence of referential integrity (foreign key) constraints. In addition, custom mapping operations may be performed during the migration operations so that the data from the source database is modified before writing the data to the target database.

Claims

1. A method for migrating data between a first database and a second database, the method comprising the steps of:

determining, by a processing unit in a computer, dependencies among a plurality of tables in the first database;

storing the determined dependencies to indicate the table dependencies;

retrieving metadata from the first database, wherein the metadata includes definitions for tables in the first database;

storing the retrieved metadata;

reading data from tables in the first database using a plurality of read operations, wherein the read operations are structured in accordance with the retrieved metadata, and wherein the read operations are in an order indicated by the determined dependencies; and

writing data to the second database using a plurality of write operations, wherein the write operations are in an order indicated by the determined dependencies.

2. The method of claim 1 further comprising:

performing a predetermined modification operation on the data read from the tables in the first database prior to a write operation to the second database.

3. The method of claim 2 further comprising:

storing the predetermined modification operation using markup language to identify the predetermined modification operation.

4. The method of claim 2 wherein the predetermined modification operation comprises assigning a default value to a field in a table in the second database that does not have a corresponding field in a corresponding table in the first database.

5. The method of claim 1 wherein the first database and the second database have dissimilar schemas.

6. The method of claim 1 wherein the write operations are in an order indicated by the determined dependencies to ensure referential integrity in the second database.