Extend crud to support lifecyle management and business continuity

• US 8,996,466 B2
• Filed: 12/01/2008
• Issued: 03/31/2015
• Est. Priority Date: 12/01/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Driesen, Volker
• Primary Examiner(s): Jacob, Ajith
• Application Number:
  US12/326,025
• Publication Number:
  US 20100138440A1
• Time in Patent Office: 2,311 Days
• Field of Search: 707/640
• US Class Current: 707/640
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/2445 Data retrieval commands; View definitions
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

The subject matter disclosed herein provides methods and apparatus, including computer program products, for providing software updates. In one aspect there is provided a method. The method may include receiving a command for execution at a database. Moreover, a determination may be made as to whether the received command is one of a set of extended commands. The set of extended commands includes lock read, lock write, migrate, copy, and log changes. The received command is executed at the database. Related systems, apparatus, methods, and/or articles are also described.

Claims

1. A non-transitory computer-readable storage medium containing instructions to configure a processor to perform a method, the method comprising:

receiving a command for execution at a database;

determining whether the received command is one of a set of extended commands, the set of extended commands comprises a lock read, a lock write, a migrate, a copy, and a log changes, the set of extended commands configure a persistency at the database based on a structure and format of a persistency at a shadow database;

the configuration of the persistency includes

executing the lock write command to prevent a write to at least one of the database and the shadow database;

initiating, based on the executed lock write command, the migrate command, the migrate function including a delta module to transform data stored in a first format of an older structure of an object stored to a data in a second format of a newer structure of the object for storage, wherein the object is stored at least one of the database and the shadow database;

enabling the log changes command to record changes to at least one of the database and the shadow database resulting from the at least one of the following the executing of the lock write command and the initiating of the migrate command;

applying, using the migrate command, changes recorded by the log changes command to the database; and

releasing the lock write command;

and

executing the received command at the database, when the received command is one of the set of extended commands, wherein when the write lock is attempted, an error message is sent.

2. The computer-readable storage medium according to claim 1, wherein the processor is further configured to perform

implementing the extended set of commands as part of a maintenance process, wherein

the lock read configured to lock data to disable reads at a first system,

the lock write configured to lock data to disable writes at the first system,

the migrate configured to migrate a portion of data from the first system to a second system, the migrated data being reformatted in accordance with a format of the second system,

the copy configured to copy another portion of data from the first system to the second system, and

the log changes configured to log changes made to data at the first system to enable the changes to be applied to the second system.

3. The computer-readable medium of claim 1, wherein the lock read prevents a read to an entry of the database and, when the read is attempted, an error message is sent.

4. The computer-readable medium of claim 1 further comprising:

executing, during a migration from a first system to a second system, the lock read for an entry in the database.

5. The computer-readable medium of claim 1, wherein the copy creates an exact copy of data, wherein during the copy, checks are not executed.

6. The computer-readable medium of claim 1, wherein the migrate transforms an older structure of an object in the database to a newer structure.

7. The computer-readable medium of claim 1, wherein the log changes record a change operation to an entry of the database, the change comprising at least one of adding a new entry, changing an existing entry, and deleting an entry.

8. The computer-readable medium of claim 7, wherein the log changes record the change operation including a timestamp indicative of when the change operation was made, a key describing the entry being changed, and a content representative of the change operation.

9. A method comprising:

receiving a command for execution at a database;

determining whether the received command is one of a set of extended commands, the set of extended commands comprises a lock read, a lock write, a migrate, a copy, and a log changes, the set of extended commands configure a persistency at the database based on a structure and format of a persistency at a shadow database;

the configuration of the persistency includes

executing the lock write command to prevent a write to at least one of the database and the shadow database;

initiating, based on the executed lock write command, the migrate command, the migrate function including a delta module to transform data stored in a first format of an older structure of an object stored to a data in a second format of a newer structure of the object for storage, wherein the object is stored at least one of the database and the shadow database;

enabling the log changes command to record changes to at least one of the database and the shadow database resulting from the at least one of the following the executing of the lock write command and the initiating of the migrate command;

applying, using the migrate command, changes recorded by the log changes command to the database; and

releasing the lock write command;

and

executing the received command at the database, when the received command is one of the set of extended commands, wherein when the write lock is attempted, an error message is sent.

10. The method of claim 9 further comprising:

implementing the extended set of commands as part of a maintenance process, the extended set of commands used to lock data to disable reads at a production system, to lock data to disable writes at the production system, to migrate a portion of data from the production system to a shadow system, the migrated data reformatted in accordance with a format of the shadow system, to copy another portion of data from the production system to the shadow system, log changes made to data at the production system to enable the changes to be applied to the shadow system.

11. The method of claim 9, wherein the lock read prevents a read to an entry of the database and, when the read is attempted, an error message is sent.

12. The method of claim 9, further comprising:

executing, during a data migration from a first system to a second system, the lock read for an entry in the database.

13. The method of claim 9, wherein the copy creates an exact copy of data, wherein during the copy, checks are not executed.

14. The method of claim 9, wherein the migrate transforms an older structure of an object in the database to a newer structure.

15. The method of claim 9, wherein the log changes record a change operation to an entry of the database.

16. The method of claim 15, wherein the log changes record the change operation including a timestamp indicative of when the change operation was made, a key describing the entry being changed, and a content representative of the change operation.

17. A system comprising:

a processor; and

a memory, wherein the processor and the memory are configured to perform a method comprising;

receiving a command for execution at a database;

determining whether the received command is one of a set of extended commands, the set of extended commands comprises a lock read, a lock write, a migrate, a copy, and a log changes, the set of extended commands configure a persistency at the database based on a structure and format of a persistency at a shadow database;

the configuration of the persistency includes

executing the lock write command to prevent a write to at least one of the database and the shadow database;

initiating, based on the executed lock write command, the migrate command, the migrate function including a delta module to transform data stored in a first format of an older structure of an object stored to a data in a second format of a newer structure of the object for storage, wherein the object is stored at least one of the database and the shadow database;

enabling the log changes command to record changes to at least one of the database and the shadow database resulting from the at least one of the following the executing of the lock write command and the initiating of the migrate command;

applying, using the migrate command, changes recorded by the log changes command to the database; and

releasing the lock write command;

and

executing the received command at the database, when the received command is one of the set of extended commands, wherein when the write lock is attempted, an error message is sent.

18. The system of claim 17, wherein the processor and the memory are configured to perform

implementing the extended set of commands as part of a maintenance process, the extended set of commands used to lock data to disable reads at a production system, to lock data to disable writes at the production system, to migrate a portion of data from the production system to a shadow system, the migrated data reformatted in accordance with a format of the shadow system, to copy another portion of data from the production system to the shadow system, log changes made to data at the production system to enable the changes to be applied to the shadow system.