Distributed data integration method and system

• US 5,884,310 A
• Filed: 06/14/1996
• Issued: 03/16/1999
• Est. Priority Date: 06/14/1996
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Electronic Data Systems Corporation (Perspecta, Inc.)
• Inventors: Lewis, Gerald R., Knesek, Mark D., Hoyt, Ronald A., Brichta, Harriet B., Owens, Geoffrey M.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/664,461
• Time in Patent Office: 1,005 Days
• Field of Search: 395/604, 395/610, 395/200.03, 395/200.08, 395/200.09, 395/416, 395/200.31, 395/200.33, 707/4, 707/10
• US Class Current: 1/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A data storage system (12) may include a plurality of source systems (14) and a common database server (16). Each source system (14) may include a source database (20), an extraction engine (24) and a transformation engine(26). At least two of the source systems (14) may have source databases (20) that store data in disparate formats and file structures. The extraction engine (24) may extract data from the source database (20). The transformation engine (26) may transform data extracted from the source database (20) into a common format and file structure. The common database server (16) may include a common database (32), a common database controller (34) and a load engine (48). The common database controller (34) may receive data transformed by the transformation engine (26). The load engine (48) may load the data received by the common database controller (34) into the common database (32).

Claims

1. A distributed data storage system, comprising:

a plurality of source systems, each including;

a source database, at least two of the source systems having source databases operable to store data in disparate formats and file structures;

an extraction engine operable to extract data from the source database; and

a transformation engine operable to transform data extracted from the source database into a common format and a common file structure; and

a common database server including;

a common database;

a common database controller operable to receive data transformed by the transformation engine; and

a load engine operable to load the data received by the common database controller into the common database.

2. The distributed data storage system of claim 1, wherein the common database server is remote from the source systems.

3. The distributed data storage system of claim 1, wherein the load engine is further operable to validate the data received by the common database controller.

4. The distributed data storage system of claim 1, further comprising at least one client system, the client system including an interface operable to execute a query of the common database.

5. The distributed data storage system of claim 4, wherein the client system is remote from the common database server.

6. The distributed data storage system of claim 4, wherein the interface is further operable to receive data in response to the query of the common database.

7. The distributed data storage system of claim 6, wherein the interface is further operable to validate the data received in response to the query of the common database.

8. The distributed data storage system of claim 4, further comprising a client database operable to store the data received in response to the query of the common database.

9. The distributed data storage system of claim 4, the interface further comprising a maintenance engine operable to initiate execution of the query of the common database by the interface.

10. The distributed data storage system of claim 9, wherein the query is an extended query.

11. The distributed data storage system of claim 9, wherein the query is a popular query.

12. The distributed data storage system of claim 9, wherein the maintenance engine is further operable to initiate execution of the query periodically according to a schedule.

13. The distributed data storage system of claim 4, the interface further comprising a user interface operable to initiate execution of the query of the common database by the interface in response to a user request.

14. A method of storing data from a plurality of source databases, comprising the steps of:

extracting data from a first source database;

transforming the data of the first source database into a common format and a common file structure;

loading the transformed data of the first source database into a common database;

extracting data from a second source database, the first and second source databases storing data in disparate formats;

transforming the data of the second source database into the common format and the common file structure; and

loading the transformed data of the second source database into the common database.

15. The method of storing data of claim 14, further comprising the step of validating the loaded data of each source database.

16. The method of storing data of claim 15, wherein the step of validating the loaded data of one of the source databases comprises the steps of:

determining a status of the transformed data of the source database;

determining a status of the loaded data of the source database;

comparing the status of the transformed data to the status of the loaded data; and

setting an error flag if the status of the transformed data differs from the status of the loaded data.

17. The method of storing data of claim 16, wherein the transformed data of the source database is loaded into at least one table of the common database, the table including at least one field, further comprising the steps of:

determining if the table into which the transformed data of the source database was loaded is valid;

setting an error flag if the table is invalid;

determining if the field of the table is valid; and

setting an error flag if the field is invalid.

18. The method of storing data of claim 14, wherein storing data in the common database comprises the steps of:

storing in a first column of a data record an identifier uniquely identifying a subject of the data record;

storing in a second column a category name for the data record; and

storing in a third column a category value associated with the category name in the second column.

19. A method of storing data in a database table comprising the steps of:

storing in a first column of a data record an identifier uniquely identifying a subject of the data record;

storing in a second column a category name for the data record; and

storing in a third column a category value associated with the category name in the second column;

wherein modifying the table to include a new category for the subject of the data record comprises the steps of;

adding to the table a second data record for the subject;

storing in the first column of the second data record, the identifier uniquely identifying the subject of the second data record;

storing in the second column of the second data record, a name of the new category; and

storing in the third column of the second data record, a category value associated with the new category name in the second column of the second data record.