US 2013/0173541 A1Published application

Database version management system

OwnerHarish Sivasubramanian Iyer, Hemanta Dash +1inventors

InventorsHarish Sivasubramanian Iyer, Hemanta Dash, Gururaj Anjan

Life of this patent

Estimating the term…

Loading patent…

Abstract

Systems and methods for managing versions of a database are described herein. The system includes a worklist module configured to receive a plurality of change requests and generate a first worklist based on them. The plurality of change requests include instructions for modifying one of a database structure and/or master data of the database. One or more change requests may be approved from the first worklist. The worklist module generates a second worklist comprising the approved change requests. One or more change requests included in the second worklist are executed to create a version of the database. A versioning module may maintain and track a plurality of versions within the database. A comparison module may allow comparison and synchronization of the plurality of versions of the database based on the results of comparison and needs in specific environment.

Claims16

Dependent claims

A method comprising:

assigning one or more roles associated with a database to a plurality of users, wherein the roles include at least one requester, at least one reviewer, and at least one administrator, and wherein each of the roles are associated with respective privileges for facilitating the plurality of users to perform operations in relation to the database;
receiving a plurality of change requests from the at least one requester, wherein the plurality of change requests include instructions for modifying at least one of a database structure and master data of the database;
generating a first worklist comprising the plurality of change requests, wherein the first worklist is provided to the at least one reviewer for approval of the plurality of change requests in the first worklist;
generating a second worklist having a set of approved change requests, wherein the set of approved change requests comprises one or more of the plurality of change requests of the first worklist that are approved by the at least one reviewer, and wherein the second worklist is provided to the at least one administrator for executing the one or more approved change requests from the set of approved change requests;
and
executing the one or more approved change requests from the set of approved change requests based on the second worklist, wherein the execution of the one or more approved change requests from the set of approved change requests creates a plurality of versions of the database, and wherein each of the plurality of versions is maintained within the database.

3 more elements

A database version management system comprising:

a processor;
and
a memory coupled to the processor, the memory comprising:
a worklist module configured to,
receive a plurality of change requests from at least one requester, wherein the plurality of change requests include instructions for modifying at least one of a database structure and a master data of a database;
generate a first worklist based on the plurality of change requests, wherein the first worklist is provided to at least one reviewer for approval;
generate a second worklist comprising one or more change requests that are approved by the at least one reviewer based on the first worklist, and wherein the second worklist is provided to at least one administrator for executing one or more change requests included in the second worklist;
and
execute the one or more change requests included in the second worklist, wherein the execution of each of the change requests included in the second worklist creates a version of the database, and wherein the versions are maintained within the database;
and
a versioning module configured to,
track a plurality of versions of the database, wherein each of the plurality of versions is created by execution of a change request selected from the second worklist;
and
maintain the plurality of versions within the database.

11 more elements

Dependencies are inferred from the claim text.