Replicated database structural change management
First Claim
Patent Images
1. A method comprising:
- receiving structural change input to structurally change a master database;
obtaining a first lock that locks at least a portion of the master database to prevent updates to the locked portion of the master database;
after obtaining the first lock, waiting for a replication process that replicates at least some data stored in the master database to a replicate database to empty a data replication buffer; and
after obtaining the first lock and after waiting for the replication process to empty the data replication buffer, obtaining a second lock that locks the replication process to prevent data replication from the master database to the replicate database;
processing the structural change input to structurally change the master database;
automatically generating a change bundle including a representation of the structural changes to the master database from which the structural changes are replicable within the replicate database;
transmitting the change bundle to a structural change process that executes against the replicate database to implement the structural changes represented in the change bundle; and
releasing the first lock and the second lock in response to a received notification indicating the structural changes have been made to the replicate database.
2 Assignments
0 Petitions
Accused Products
Abstract
The various embodiments herein include at least one of systems, methods, and software that operate to replicate structural changes made to a master database to a replicate database. In some such embodiments, changes made to a master database are identified and a representation thereof is provided to a process that implements such changes in the replicate database. The structural changes are then replicated in the replicate database.
24 Citations
20 Claims
-
1. A method comprising:
-
receiving structural change input to structurally change a master database; obtaining a first lock that locks at least a portion of the master database to prevent updates to the locked portion of the master database; after obtaining the first lock, waiting for a replication process that replicates at least some data stored in the master database to a replicate database to empty a data replication buffer; and after obtaining the first lock and after waiting for the replication process to empty the data replication buffer, obtaining a second lock that locks the replication process to prevent data replication from the master database to the replicate database; processing the structural change input to structurally change the master database; automatically generating a change bundle including a representation of the structural changes to the master database from which the structural changes are replicable within the replicate database; transmitting the change bundle to a structural change process that executes against the replicate database to implement the structural changes represented in the change bundle; and releasing the first lock and the second lock in response to a received notification indicating the structural changes have been made to the replicate database. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A system comprising:
a computing platform including at least one processor, at least one memory device, and at least one network interface device, the at least one memory device storing instructions executable by the at least one processor to perform operations comprising; receiving, via the at least one network interface device, structural change input structurally change a master database; obtaining a first lock that locks at least a portion of the master database to prevent updates to the locked portion of the master database; and after obtaining the first lock, obtaining a second lock that locks a replication process that replicates at least some data stored in the master database to a replicate database upon a buffer of data to be replicated becoming empty; processing the structural change input to structurally change the master database; automatically generating a change bundle including a representation of the structural changes to the master database from which the structural changes are replicable within the replicate database; transmitting, via the at least one network interface device, the change bundle to a structural change process that executes against the replicate database; and releasing the first lock and the second lock in response to a received notification indicating the structural changes have been implemented in the replicate database. - View Dependent Claims (12, 13, 14, 15)
-
16. A non-transitory computer readable storage medium with instructions stored thereon which when executed in part by at least one processor of at least one computing device causes the at least one computing device to perform operations comprising:
-
receiving structural change input to structurally change a master database; Obtaining a first lock that locks at least a portion of the master database to prevent updates to the locked portion of the master database; after obtaining the first lock, waiting for a replication process that replicates at least some data stored in the master database to a replicate database to empty a data replication buffer; and after obtaining the first lock and after waiting for the replication process to empty the data replication buffer, obtaining a second lock that locks the replication process to prevent data replication from the master database to the replicate database; processing the structural change input to structurally change the master database; automatically generating a change bundle including a representation of the structural changes to the master database from which the structural changes are replicable within the replicate database; transmitting the change bundle to a structural change process that executes against the replicate database to implement the structural changes represented in the change bundle; and releasing the first lock and the second lock in response to a received notification indicating the structural changes have been made to the replicate database. - View Dependent Claims (17, 18, 19, 20)
-
Specification