US 7,415,467 B2
Database replication system
Zulfikar Jeevanjee, Webster Groves, Mo. (US); and Kenneth L. Long, O'Fallon, Mo. (US)
Assigned to Ixion, Inc., O'Fallon, Mo. (US)
Filed on Jul. 07, 2004, as Appl. No. 10/885,844.
Application 10/885844 is a continuation in part of application No. 10/795701, filed on Mar. 08, 2004, abandoned.
Claims priority of provisional application 60/452627, filed on Mar. 06, 2003.
Prior Publication US 2004/0249870 A1, Dec. 09, 2004
Int. Cl. G06F 17/30 (2006.01); G06F 17/00 (2006.01)
U.S. Cl. 707—8  [707/10] 20 Claims
OG exemplary drawing
 
1. A method for replicating a change operation performed upon an application database to a replica application database, comprising:
capturing change operations made to one or more application tables stored in an application database;
aggregating the captured change operations performed upon the one or more application tables in a memory;
monitoring the aggregated change operations to identify a triggering event corresponding to a change operation having a different execution direction; and
applying the aggregated change operations having a same execution direction to one or more replica application tables in the replica application database that correspond to the one or more application tables in the application database in a single operation in response to the identified triggering event, wherein a sequence in which each of the aggregated change operations are applied to the one or more replica tables during the single operation is based on a hierarchy level of the corresponding one or more application tables;
wherein the triggering event is the first occurrence of either of a change in execution direction of the change operation or a predetermined number of aggregated change operations being reached in the memory for an individual replica table;
wherein aggregating the change operations performed upon the application database includes aggregating the change operations to be applied to the replica database in a first sequence corresponding to the order in which the change operations where performed upon the application database, and
wherein applying the aggregated change operations includes applying the aggregated change operations in a second sequence corresponding to the hierarchy level of the corresponding one or more application tables.