Conversion of relational databases into triplestores

• US 8,037,108 B1
• Filed: 07/22/2009
• Issued: 10/11/2011
• Est. Priority Date: 07/22/2009
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Chang, Walter
• Primary Examiner(s): NGUYEN, CAM LINH T
• Application Number:
  US12/507,746
• Time in Patent Office: 811 Days
• Field of Search: 707/791, 707/793, 707/795, 707/796, 707/802, 707/803, 707/807, 707/810
• US Class Current: 707/803
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for converting a relational database into a triplestore. In one aspect, a method includes retrieving meta schema information for a relational database, including checking a data dictionary associated therewith, and saving the information (including column, primary key constraint and foreign key constraint definitions) in a canonical format; processing the saved information to identify triples to be created in a triplestore; and generating triples in the triplestore in accordance with results of the processing, the generating including: creating first triples (corresponding to data specified within relational database tables) using the column definitions, creating second triples (corresponding to data links between the relational database tables) using the primary key and foreign key constraint definitions, and creating third triples using a primary key constraint definition, a foreign key constraint definition, and an associative mapping table corresponding to the relational database.

Claims

1. A method comprising:

retrieving meta schema information for a relational database, including checking a data dictionary associated with the relational database, and saving the meta schema information in a canonical format, the saved meta schema information comprising column definitions, primary key constraint definitions and foreign key constraint definitions obtained from the data dictionary;

processing the saved meta schema information to identify triples to be created in a triplestore; and

generating triples in the triplestore in accordance with results of the processing, the generating comprising;

creating first triples using the column definitions, the first triples corresponding to data specified within tables in the relational database,

creating second triples using the primary key constraint definitions and the foreign key constraint definitions, the second triples corresponding to data links between the tables in the relational database, and

creating third triples using at least one of the primary key constraint definitions, at least one of the foreign key constraint definitions, and an associative mapping table corresponding to the relational database;

where the retrieving and saving, the processing, and the generating are performed by one or more data processing apparatus.

2. The method of claim 1, where the retrieving and saving comprises:

reading names of table views to be mapped from the relational database;

reading definitions of columns for each table to be mapped from the relational database;

saving a definition for each table to be mapped from the relational database;

saving primary key, foreign key and alternate key definitions for tables to be mapped from the relational database; and

saving definitions of primary key, foreign key and alternate key constraints for tables to be mapped from the relational database.

3. The method of claim 2, where the processing comprises building a schema metamodel graph for the relational database, the schema metamodel graph comprising an expansion list for each table to be mapped from the relational database and a graph adjacency list indicating connections between rows of different tables through primary key to foreign key relationships.

4. The method of claim 3, where the processing comprises traversing the schema metamodel graph for the relational database to preserve referential integrity rules with respect to the relational database, the traversing comprising:

expanding table rows including expanding a given row into individual triples, each of the individual triples comprising a subject including primary-key information from the given row, a predicate including column name information from the given row, and an object including non-primary-key information from the given row;

determining mapping structures for primary key to foreign key and alternate key to foreign key pairs in accordance with a canonical mapping template;

normalizing keys to support collation and sorting; and

creating intermediate associative map triple-entities to maintain source-destination mappings when one-to-many or many-to-many primary key to foreign key relationships are present.

5. The method of claim 4, where the generating comprises re-traversing the schema metamodel graph and, for each edge in the schema metamodel graph:

creating RDF-triplestore link triples to represent each primary key to foreign key and alternate key to foreign key relationship; and

storing each new RDF-triplestore link triple in the triplestore.

6. The method of claim 1, further comprising:

creating inverse triples based on information found in the data dictionary associated with the relational database; and

creating inverse triples based on information found in relational query optimizer statistics retrieved from a relational database management system of the relational database.

7. A computer storage medium encoded with a computer program, the program comprising instructions that when executed by data processing apparatus cause the data processing apparatus to perform operations comprising:

retrieving meta schema information for a relational database, including checking a data dictionary associated with the relational database, and saving the meta schema information in a canonical format, the saved meta schema information comprising column definitions, primary key constraint definitions and foreign key constraint definitions obtained from the data dictionary;

processing the saved meta schema information to identify triples to be created in a triplestore; and

generating triples in the triplestore in accordance with results of the processing, the generating comprising;

creating first triples using the column definitions, the first triples corresponding to data specified within tables in the relational database,

creating second triples using the primary key constraint definitions and the foreign key constraint definitions, the second triples corresponding to data links between the tables in the relational database, and

creating third triples using at least one of the primary key constraint definitions, at least one of the foreign key constraint definitions, and an associative mapping table corresponding to the relational database.

8. The computer storage medium of claim 7, where the retrieving and saving comprises:

reading names of table views to be mapped from the relational database;

reading definitions of columns for each table to be mapped from the relational database;

saving a definition for each table to be mapped from the relational database;

saving primary key, foreign key and alternate key definitions for tables to be mapped from the relational database; and

saving definitions of primary key, foreign key and alternate key constraints for tables to be mapped from the relational database.

9. The computer storage medium of claim 8, where the processing comprises building a schema metamodel graph for the relational database, the schema metamodel graph comprising an expansion list for each table to be mapped from the relational database and a graph adjacency list indicating connections between rows of different tables through primary key to foreign key relationships.

10. The computer storage medium of claim 9, where the processing comprises traversing the schema metamodel graph for the relational database to preserve referential integrity rules with respect to the relational database, the traversing comprising:

expanding table rows including expanding a given row into individual triples, each of the individual triples comprising a subject including primary-key information from the given row, a predicate including column name information from the given row, and an object including non-primary-key information from the given row;

determining mapping structures for primary key to foreign key and alternate key to foreign key pairs in accordance with a canonical mapping template;

normalizing keys to support collation and sorting; and

creating intermediate associative map triple-entities to maintain source-destination mappings when one-to-many or many-to-many primary key to foreign key relationships are present.

11. The computer storage medium of claim 10, where the generating comprises re-traversing the schema metamodel graph and, for each edge in the schema metamodel graph:

creating RDF-triplestore link triples to represent each primary key to foreign key and alternate key to foreign key relationship; and

storing each new RDF-triplestore link triple in the triplestore.

12. The computer storage medium of claim 7, the operations further comprising:

creating inverse triples based on information found in the data dictionary associated with the relational database; and

creating inverse triples based on information found in relational query optimizer statistics retrieved from a relational database management system of the relational database.

13. A system comprising:

a user device;

a relational database management system; and

one or more computers operable to interact with the user device and the relational database management system and to perform operations comprising;

retrieving meta schema information for a relational database, including checking a data dictionary associated with the relational database, and saving the meta schema information in a canonical format, the saved meta schema information comprising column definitions, primary key constraint definitions and foreign key constraint definitions obtained from the data dictionary;

processing the saved meta schema information to identify triples to be created in a triplestore; and

generating triples in the triplestore in accordance with results of the processing, the generating comprising;

creating first triples using the column definitions, the first triples corresponding to data specified within tables in the relational database,

creating second triples using the primary key constraint definitions and the foreign key constraint definitions, the second triples corresponding to data links between the tables in the relational database, and

creating third triples using at least one of the primary key constraint definitions, at least one of the foreign key constraint definitions, and an associative mapping table corresponding to the relational database.

14. The system of claim 13, where the retrieving and saving comprises:

reading names of table views to be mapped from the relational database;

reading definitions of columns for each table to be mapped from the relational database;

saving a definition for each table to be mapped from the relational database;

saving primary key, foreign key and alternate key definitions for tables to be mapped from the relational database; and

saving definitions of primary key, foreign key and alternate key constraints for tables to be mapped from the relational database.

15. The system of claim 14, where the processing comprises building a schema metamodel graph for the relational database, the schema metamodel graph comprising an expansion list for each table to be mapped from the relational database and a graph adjacency list indicating connections between rows of different tables through primary key to foreign key relationships.

16. The system of claim 15, where the processing comprises traversing the schema metamodel graph for the relational database to preserve referential integrity rules with respect to the relational database, the traversing comprising:

expanding table rows including expanding a given row into individual triples, each of the individual triples comprising a subject including primary-key information from the given row, a predicate including column name information from the given row, and an object including non-primary-key information from the given row;

determining mapping structures for primary key to foreign key and alternate key to foreign key pairs in accordance with a canonical mapping template;

normalizing keys to support collation and sorting; and

creating intermediate associative map triple-entities to maintain source-destination mappings when one-to-many or many-to-many primary key to foreign key relationships are present.

17. The system of claim 16, where the generating comprises re-traversing the schema metamodel graph and, for each edge in the schema metamodel graph:

creating RDF-triplestore link triples to represent each primary key to foreign key and alternate key to foreign key relationship; and

storing each new RDF-triplestore link triple in the triplestore.

18. The system of claim 13, the operations further comprising:

creating inverse triples based on information found in the data dictionary associated with the relational database; and

creating inverse triples based on information found in relational query optimizer statistics retrieved from a relational database management system of the relational database.

19. The system of claim 13, wherein the one or more computers comprise a server operable to interact with the user device through a data communication network, and the user device is operable to interact with the server as a client.

20. The system of claim 13, wherein the one or more computers consist of one computer, the user device is a user interface device, and the one computer comprises the user interface device.