Method and system for re-population of data in a database

• US 7,516,144 B2
• Filed: 09/27/2006
• Issued: 04/07/2009
• Est. Priority Date: 10/28/2005
• Status: Expired due to Fees

• Current Assignee: Vaakya Technologies Private Limited
• Original Assignee: Vaakya Technologies Private Limited
• Inventors: Lakshminarasimhan, Muralidharan Kanchi
• Primary Examiner(s): Le; Uyen T.
• Application Number:
  US11/535,491
• Publication Number:
  US 20070100791A1
• Time in Patent Office: 923 Days
• Field of Search: 707/1, 707/100, 707/200
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24565 Triggers; Constraints
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A method for automatic re-population of data in a database in response to detection of at least one script-transaction, the database includes a plurality of tables. The script-transaction is carried out in response to a script input. The method includes truncating at least one table, which is being modified by at least one of a persistent trigger and a non-persistent trigger. The persistent trigger updates a table and the non-persistent trigger performs one of an insert operation and a delete operation on a table. Further, the method includes executing a non-persistent trigger corresponding to each truncated table of the database in a predefined-update-sequence. Also, the method includes executing at least one persistent trigger corresponding to each truncated table of the database.

Claims

1. A database management system, the database management system managing a database, the database comprising a plurality of tables, the database management system comprising:

a processor; and

a memory coupled to the processor;

a. a classifier residing in the memory, classifies each database trigger into one of a persistent trigger and a non-persistent trigger, wherein a persistent trigger updates a table and a non-persistent trigger performs one of an insert operation and a delete operation on a table;

b. a categorizer residing in the memory, categorizes each table into one of a no-trigger-table, a non-persistent-trigger-table and a persistent-trigger-table, wherein a no-trigger-table is a table that is not modified by a trigger, a non-persistent-trigger-table is a table that is modified by a non-persistent trigger, and a persistent-trigger-table is a table that is modified by a persistent trigger;

c. a sequencing module residing in the memory, the sequencing module sequencing each table into a predefined-update-sequence;

d. a detection module residing in the memory, the detection module detecting at least one script-transaction, wherein the script-transaction is result of a structural change in the database, the at least one script-transaction being carried out in response to a script input; and

e. a re-population module residing in the memory, the re-population module re-populating data in the database in response to the detection module detecting the at least one script-transaction.

2. The database management system of claim 1, wherein the re-population module comprises:

a. a truncating module, the truncating module truncating at least one table, wherein a table of the at least one table is one of the non-persistent-trigger-table and the persistent-trigger-table;

b. a non-persistent-trigger-executing module, the non-persistent-trigger-executing module, executing a non-persistent trigger corresponding to each truncated table of the database in the predefined-update-sequence; and

c. a persistent-trigger-executing module, the persistent-trigger-executing module executing at least one persistent trigger corresponding to each truncated table of the database.

3. A method for enabling automatic re-population of data in a database, the database comprising a plurality of tables, the method comprising:

a. classifying each database trigger into one of a persistent trigger and a non-persistent trigger, wherein a persistent trigger modifies a table and a non-persistent trigger performs one of an insert operation and a delete operation on a table; and

b. categorizing each table into one of a no-trigger-table, a non-persistent-trigger-table and a persistent-trigger-table, wherein a no-trigger-table is not modified by a trigger, a non-persistent-trigger-table is modified by a non-persistent trigger, and persistent-trigger-table is modified by a persistent trigger.

4. The method of claim 3, wherein a database trigger is one of a plurality of update-trigger, a plurality of delete-trigger and a plurality of insert-triggers.

5. A method for automatic re-population of data in a database comprising a plurality of tables, the method comprising:

a. truncating at least one table in response to detection of at least one script-transaction, wherein the script-transaction is result of a structural change in the database, and wherein a table of the at least one table is one of a non-persistent-trigger-table and a persistent-trigger-table, and wherein a non-persistent-trigger-table is modified by a non-persistent trigger and a persistent-trigger-table is modified by a persistent trigger, and wherein a persistent trigger updates a table and a non-persistent trigger performs one of an insert operation and a delete operation on a table;

b. executing a non-persistent trigger corresponding to each truncated table in a predefined-update-sequence; and

c. executing at least one persistent trigger corresponding to each truncated table for automatic re-population of data in the database.

6. The method of claim 5, wherein the script-transaction is result of data corruption in the database.

7. The method of claim 5 further comprises creating at least one additional table in order to execute the at least one non-persistent trigger.

8. The method of claim 5, wherein a non-persistent trigger further updates a table.

9. The method of claim 5, wherein the structural change in the database is result of a change in a business rule.

10. The method of claim 5, wherein structural change in the database comprises change in structure of at least one secondary table in the database, wherein the at least one secondary table is updated by at least one of the persistent trigger and the non-persistent trigger.

11. The method of claim 10, wherein the at least one secondary table is updated by at most one non-persistent trigger.

12. A computer program product for use with a computer, the computer program product comprising a computer usable medium having a computer readable program code embodied therein for automatic re-population of data in a database comprising a plurality of tables, the computer code performing:

a. truncating at least one table in response to at least one script-transaction, wherein the script-transaction is result of a structural change in the database, and wherein a table of the at least one table is one of a non-persistent-trigger-table and a persistent-trigger-table, and wherein a non-persistent-trigger-table is modified by a non-persistent trigger and a persistent-trigger-table is modified by a persistent trigger, and wherein a persistent trigger updates a table and a non-persistent trigger performs one of an insert operation and a delete operation on a table;

b. executing a non-persistent trigger corresponding to each truncated table of the database in a predefined-update-sequence; and

c. executing at least one persistent trigger corresponding to each truncated table of the database for automatic re-population of data in the database.