Zero downtime upgrade for database applications using tables with sequences

Patent metadata

Field	Value
Publication number	US-9898494-B2
Application number	US-201514629409-A
Country	US
Kind code	B2
Filing date	Feb 23, 2015
Priority date	Feb 23, 2015
Publication date	Feb 20, 2018
Grant date	Feb 20, 2018

Abstract

An upgrade of a first version of a database application to a second version of a database application that both have a same data schema is initiated. The first database application has a first access schema such that at least one table in the data schema is linked to the first access schema. The second version of the database application has a second access schema such that at least one database table in the data schema is linked to the second access schema. The first access schema differs from the second access schema. Concurrent access is provided for each access schema to at least one sequence in the data schema to both the first version of the database application and the second version of the database application. Related apparatus, systems, techniques and articles are also described.

First claim

What is claimed is:

1. A method for implementation by one or more data processors forming part of at least one computing device, the method comprising:
initiating an upgrade of a first version of a database application to a second version of a database application that both have a same data schema, the first database application having a first access schema such that at least one database table in the data schema is linked to the first access schema, the second version of the database application having a second access schema such that the at least one database table in the data schema is linked to the second access schema, the first access schema differing from the second access schema; and
providing, for each access schema, concurrent access to a sequence in the data schema to both the first version of the database application and the second version of the database application, the sequence being configured to generate, in response to a first call from the first access schema, a first unique value for a first new row of data being inserted into the at least one database table, the sequence being further configured to generate, in response to a second call from the second access schema, a second unique value for a second new row of data being inserted into the at least one database table, the first unique value and the second unique value being generated by at least incrementing a current value of the sequence.

2. The method of claim 1 , wherein the concurrent access is enabled by a respective at least one sequence pointer in each of the first access schema and the second access schema.

3. The method of claim 1 , wherein the concurrent access is enabled by a field in a respective at least one table in each of the first access schema and the second access schema.

4. The method of claim 3 , wherein each of the first access schema and the second access schema includes a table pointer to the at least one database table in the data schema.

5. The method of claim 1 further comprising:
providing, for each access schema, concurrent access to at least one database table in the data schema to both the first version of the database application and the second version of the database application, the concurrent access being enabled by a respective at least one table link object in each of the first access schema and the second access schema that is used by database views or stored procedures such access schema.

6. The method of claim 5 further comprising:
updating, using at least one application trigger associated with the at least one table link object, the at least one database table in the data schema to reflect changes in a corresponding table link object.

7. The method of claim 6 , wherein there is a first application trigger in the first access schema on the first table link and a second application trigger in the second access schema on a second table link, wherein only the first application trigger is called if the table in the data schema is updated through the first table link object in the first access schema and only the second application trigger is called if the table in the data schema is updated through the second table link object in the second access schema.

8. The method of claim 5 , wherein the at least one table link object specifies a select field list of the at least one table in the data schema, wherein the list of fields specified by the table link object is smaller than the list of fields of the table.

9. The method of claim 5 , wherein the at least one table link object is used by a database object that cannot use a database view.

10. The method of claim 5 , wherein at least one table link object specifies a calculated field.

11. The method of claim 10 , wherein the calculated field is transient.

12. The method of claim 5 , wherein the at least one table link object references a table in the data schema that specifies a calculated field.

13. The method of claim 1 , wherein the database application is executed using an in-memory database system.

14. A system comprising:
at least one data processor; and
memory storing instructions which, when executed by the at least one data processor, result in operations comprising:
initiating an upgrade of a first version of a database application to a second version of a database application that both have a same data schema, the first database application having a first access schema such that at least one database table in the data schema is linked to the first access schema, the second version of the database application having a second access schema such that the at least one database table in the data schema is linked to the second access schema, the first access schema differing from the second access schema; and
providing, for each access schema, concurrent access to a sequence in the data schema to both the first version of the database application and the second version of the database application, the sequence being configured to generate, in response to a first call from the first access schema, a first unique value for a first new row of data being inserted into the at least one database table, the sequence being further configured to generate, in response to a second call from the second access schema, a second unique value for a second new row of data being inserted into the at least one database table, the first unique value and the second unique value being generated by at least incrementing a current value of the sequence.

15. The system of claim 14 , wherein the concurrent access is enabled by a respective at least one sequence pointer in each of the first access schema and the second access schema.

16. The system of claim 14 , wherein the concurrent access is enabled by a field in a respective at least one table in each of the first access schema and the second access schema.

17. The system of claim 16 , wherein each of the first access schema and the second access schema includes a table pointer to the at least one database table in the data schema.

18. The system of claim 17 , wherein the operations further comprise:
providing, for each access schema, concurrent access to at least one database table in the data schema to both the first version of the database application and the second version of the database application, the concurrent access being enabled by a respective at least one table link object in each of the first access schema and the second access schema that is used by database views or stored procedures such access schema; and
updating, using at least one application trigger associated with the at least one table link object, the at least one database table in the data schema to reflect changes in a corresponding table link object.

19. The system of claim 18 , wherein there is a first application trigger in the first access schema on the first table link and a second application trigger in the second access schema on a second table link, wherein only the first application trigger is called if the table in the data schema is updated through the first table link object in the first access schema and only the second application trigger is called if the table in the data schema is updated through the second table link object in the second access schema.

20. A non-transitory computer program product storing instructions which, when executed by at least one data processor forming part of at least one computing device, result in operations comprising:
initiating an upgrade of a first version of a database application to a second version o

Assignees

• Eberlein Peter
• Driesen Volker
• Sap Se

Inventors

• Eberlein Peter
• Driesen Volker

Classifications

• G06F16/2315 Primary

  Optimistic concurrency control · CPC title

• G06F16/213

  with details for schema evolution support · CPC title

• G06F8/656

  while running · CPC title

• G06F8/67

  Physics · mapped topic

• G06F17/30297

  Physics · mapped topic