HYBRID DATABASE UPGRADE MIGRATION

• US 20150363452A1
• Filed: 06/15/2014
• Published: 12/17/2015
• Est. Priority Date: 06/15/2014
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Tu, Enping, Ma, Yanlun, Chen, Yung-Yin
• Granted Patent: US 9,779,126 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/213 with details for schema evolution support
• CPC Class Codes: G06F 16/2329 using versioning

Abstract

According to some embodiments, it may be determined that a plurality of hybrid database version upgrade migrations are to be performed. Each upgrade migration may include, for example, a schema change portion and a data change portion. A first database migration tool instance may be automatically run to perform the upgrade migration schema change portions. Similarly, a second database migration tool instance may be automatically run to perform the upgrade migration data change portions, wherein the second instance is not run until the first instance is complete.

Claims

1. A method, comprising:

determining that a plurality of hybrid database version upgrade migrations are to be performed, each upgrade migration including a schema change portion and a data change portion;

automatically running a first database migration tool instance to perform the upgrade migration schema change portions; and

automatically running a second database migration tool instance to perform the upgrade migration data change portions,

wherein the second instance is not run until the first instance is complete.

2. The method of claim 1, wherein the two instances use independent metadata schema tables to track migrated versions.

3. The method of claim 2, wherein each schema change portion and data change portion is associated with a version number,

the first instance performs the schema change portions in order based on the version number, beginning with the first version number that is not in the metadata schema table associated with the schema change portions, and

the second instance performs the data change portions in order based on the version number, beginning with the first version number that is not in the metadata schema table associated with the data change portions.

4. The method of claim 1, wherein the schema portions comprise structured query language portions.

5. The method of claim 1, wherein the data portions comprise Java code portions.

6. The method of claim 1, wherein the hybrid database version upgrade migration is associated with a cloud environment.

7. The method of claim 6, wherein a transaction manager provides multi-tenant functionality for the hybrid database version upgrade migration.

8. The method of claim 7, further comprising, prior to running the instances:

establishing a schema change file repository to store schema change migration code;

establishing a data change file repository to store data change migration code; and

establishing a structured query language file repository to store statements to be executed by the database migration tool.

9. The method of claim 8, wherein the schema or data change file repositories further store migration rollback code.

10. The method of claim 9, further comprising:

upon an exception associated with one of hybrid database version upgrade migrations, executing the migration rollback code such that all tenants are associated with the same database version.

11. The method of claim 1, wherein said determining is associated with at least one of:

(i) a startup process, (ii) an administrator, (iii) a developer, (iv) a periodic process, and (v) an arrival of a new hybrid database version upgrade migration.

12. The method of claim 1, wherein the hybrid database version upgrade migration is associated with at least one of:

(i) a development environment, (ii) a test environment, (iii) a production environment, (iv) an initial database version, (v) a patch, (vi) a new release, and (vii) a new database feature.

13. A non-transitory computer-readable medium storing program code, the program code executable by a computer processor to perform a method, wherein the method comprises:

determining that a plurality of hybrid database version upgrade migrations are to be performed, each upgrade migration including a schema change portion and a data change portion;

automatically running a first database migration tool instance to perform the upgrade migration schema change portions; and

automatically running a second database migration tool instance to perform the upgrade migration data change portions,

wherein the second instance is not run until the first instance is complete.

14. The medium of claim 13, wherein the two instances use independent metadata schema tables to track migrated versions, and each schema change portion and data change portion is associated with a version number,

the first instance performs the schema change portions in order based on the version number, beginning with the first version number that is not in the metadata schema table associated with the schema change portions, and

the second instance performs the data change portions in order based on the version number, beginning with the first version number that is not in the metadata schema table associated with the data change portions.

15. The medium of claim 13, wherein the schema portions comprise structured query language portions and the data portions comprise Java code portions.

16. The medium of claim 13, wherein the hybrid database version upgrade migration is associated with a cloud environment and a transaction manager provides multi-tenant functionality for the hybrid database version upgrade migration.

17. A system, comprising:

a storage device to store a plurality of hybrid database version upgrade migrations, each upgrade migration including a schema change portion and a data change portion;

a computer processor coupled to the storage device and configured to;

(i) run a first database migration tool instance to perform the upgrade migration schema change portions, and (ii) run a second database migration tool instance to perform the upgrade migration data change portions, wherein the second instance is not run until the first instance is complete.

18. The system of claim 17, wherein the two instances use independent metadata schema tables to track migrated versions, and each schema change portion and data change portion is associated with a version number,

the first instance performs the schema change portions in order based on the version number, beginning with the first version number that is not in the metadata schema table associated with the schema change portions, and

the second instance performs the data change portions in order based on the version number, beginning with the first version number that is not in the metadata schema table associated with the data change portions.

19. The system of claim 17, wherein the schema portions comprise structured query language portions and the data portions comprise Java code portions.

20. The system of claim 17, wherein the hybrid database version upgrade migration is associated with a cloud environment and a transaction manager provides multi-tenant functionality for the hybrid database version upgrade migration.