Method and system for dynamic data merge in databases

• US 7,493,344 B2
• Filed: 04/03/2006
• Issued: 02/17/2009
• Est. Priority Date: 04/01/2005
• Status: Active Grant

• Current Assignee: Schlumberger Technology Corporation (Schlumberger NV)
• Original Assignee: Schlumberger Technology Corporation (Schlumberger NV)
• Inventors: Prabhakaran, Muralidhar, Wald, Joe
• Primary Examiner(s): NGUYEN, CAM LINH T
• Application Number:
  US11/397,947
• Publication Number:
  US 20060224638A1
• Time in Patent Office: 1,051 Days
• Field of Search: 707/1, 707/3, 707/4, 707/10, 707/6, 707100-1041
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99936 Pattern matching access
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A data repository defined by a single logical specification includes a data store including a plurality of tables and a view of the plurality of tables, a data dictionary including a meta-table and means to generate the data store, where the meta-table is generated from the single logical specification defining the data repository, and a merge engine configured to merge incoming data with the data store based on match attributes defined by the single logical specification, where the incoming data is stored in at least one staging area.

Claims

1. A method to merge incoming data with data in a data store having a plurality of tables, comprising:

loading an incoming entity into a staging area in a server, wherein the staging area comprises a replica of the plurality of tables;

identifying a first match attribute of the incoming entity from a match table, wherein the first match attribute is associated with a first rank;

identifying a second match attribute of the incoming entity from the match table, wherein the second match attribute is a match entity and is associated with a second rank;

identifying a third match attribute of the match entity from the match table; and

generating a plurality of match rules based on the first match attribute and the third match attribute, wherein an order of the plurality of match rules is based on the first rank and the second rank;

executing the plurality of match rules according to the order to identify an entity in the datastore matching the incoming entity; and

updating the entity in the datastore based on the incoming entity.

2. The method of claim 1, further comprising:

checking for entities of data with instances populated in the staging area.

3. The method of claim 1, further comprising:

deleting a duplicate of the incoming entity from the staging area prior to identifying the first match attribute.

4. The method of claim 1, further comprising:

identifying a link of the incoming entity violating referential integrity; and

setting the link of the incoming entity to a value ignored by the merge.

5. A computer readable medium storing instructions to merge incoming data with data in a data store having a plurality of tables, the instructions comprising functionality to:

load an incoming entity into a staging area in a server, wherein the staging area comprises a replica of the plurality of tables;

identify a first match attribute of the incoming entity from a match table, wherein the first match attribute is associated with a first rank;

identify a second match attribute of the incoming entity from the match table, wherein the second match attribute is a match entity and is associated with a second rank;

identify a third match attribute of the match entity from the match table; and

generate a plurality of match rules based on the first match attribute and the third match attribute, wherein an order of the plurality of match rules is based on the first rank and the second rank;

execute the plurality of match rules according to the order to identity an entity in the datastore matching the incoming entity; and

update the entity in the datastore based on the incoming entity.

6. The computer readable medium of claim 5, further comprising:

checking for entities with instances populated in the staging area.

7. The computer readable medium of claim 5, further comprising:

deleting a duplicate of the incoming entity from the staging area prior to identifying the first match attribute.

8. The computer readable medium of claim 5, further comprising:

identifying a link of the incoming entity violating referential integrity; and

setting the link of the incoming entity to a value ignored during the merge.