Low maintenance data delivery and refresh system for decision support system database

• US 5,787,415 A
• Filed: 10/30/1996
• Issued: 07/28/1998
• Est. Priority Date: 10/30/1996
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Jacobson, Paul, Tefft, Michael
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/739,531
• Time in Patent Office: 636 Days
• Field of Search: 707/1, 707/2, 707/4, 707/200, 707/100
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing

Abstract

Processing overhead for maintenance of integrity of one or more de-normalized relational databases including an entity-attribute-relationship architecture during updates thereof in a decision support system is expedited by transfer and merger of data by use of standard utilities under control of control files corresponding to the database architecture. Complexity of maintenance of the database as the database architecture is changed is minimized by alteration of the control files but not the utilities or the complex protocols of previously known systems. By thus reducing processing overhead when updating and/or refreshing of the database(s) is to be done, data may be efficiently maintained with improved currency while enhancing availability of the system to the user. Efficiency of the decision support system is improved since de-normalization may be accommodated by the modification of control files which are preferably in the form of SQL statements and thus the database architecture can be readily optimized at will or adaptively for high search efficiency.

Claims

1. A method for maintaining data integrity of a decision support system when data is to be updated/refreshed in one or more de-normalized relational databases therein, said a de-normalized database having an entity-attribute-relationship architecture, said method comprising the steps, in sequence, of

collecting update data in a staging table corresponding to an entity or database,

identifying instances of an entity to be updated in a home entity table of said decision support system,

erasing instances of an entity in said home entity table of said decision support system which are identified by said identifying step,

merging said update data with import data from instances in another entity or database to form merged data, and

storing said merged data as instances in said home entity table of said decision support system.

2. A method as recited in claim 1, including the further step of

generating a unique identifier signal.

3. A method as recited in claim 2, wherein said merging step includes the further step of

merging said unique identifier signal with said update data and said import data from instances in another entity or database to form said merged data.

4. A method as recited in claim 1, including the further step of

exporting data from said home entity table of said decision support system to another entity or database.

5. A method as recited in claim 4, wherein said exporting step includes the further steps of

copying another entity or database into a reference staging table,

merging data copied into said reference staging table with export data from instances in said home entity table decision support system to form additional merged data, and

storing said additional merged data as instances in said another entity or database of said decision support system.

6. A method as recited in claim 3, including the further step of exporting data from said home entity table of said decision support system to another entity or database.

7. A method as recited in claim 6, wherein said exporting step includes the further steps of

copying another entity or database of said into a reference staging table,

merging data copied into said reference staging table with export data from instances in said home entity table of said decision support system to form additional merged data, and

storing said additional merged data as instances in said another entity or database of said decision support system.

8. A method as recited in claim 1, including the further steps of

copying said home entity table of said decision support system into a reference staging table, and wherein said merging step includes

merging data in said reference staging table with said update data and said import data from instances in another entity or database to form said merged data.

9. A method as recited in claim 3, including the further steps of

copying said home entity table of said decision support system into a reference staging table, and wherein said merging step includes

merging data in said reference staging table with said update data, said unique identifier and said import data from instances in another entity or database to form said merged data.

10. A method as recited in claim 8, including the further step of

exporting data from said home entity table of said decision support system to another entity or database.

11. A method as recited in claim 10, wherein said exporting step includes the further steps of

copying another entity or database of said into a reference staging table,

merging data copied into said reference staging table with export data from instances in said home entity table of said decision support system to form additional merged data, and

storing said additional merged data as instances in said another entity or database of said decision support system.

12. A method as recited in claim 9, including the further step of

exporting data from said home entity table of said decision support system to another entity or database.

13. A method as recited in claim 12, wherein said exporting step includes the further steps of

copying another entity or database of said into a reference staging table,

merging data copied into said reference staging table with export data from instances in said home entity table of said decision support system to form additional merged data, and

storing said additional merged data as instances in said another entity or database of said decision support system.

14. A method as recited in claim 1, wherein data is transferred and merged by utilities under control of a control file and including the further steps of

altering said database architecture, and

altering a control file in accordance with said change in said database architecture.

15. A method as recited in claim 14, wherein said control file contains at least one SQL statement.