Database migration
A technique for converting a first version of a database to a second version is disclosed. The technique includes determining available translation steps, selecting a translation path from the first version of the database to the second version, and executing the selected translation steps in the translation path. The translation path includes selected translation steps from among the available translation steps.
1. A method of converting a first version of a database to a third version, including:
selecting, using a processor, a translation path from a plurality of translation paths based on either a shortest path or a first path found, each translation path proceeding from the first version of the database to the third version of the database via a second version of the database; and
traversing, using the processor, the selected translation path comprising:
converting the first version of the database to the second version of the database; and
converting the second version of the database to the third version of the database,
wherein the database is part of a cluster including a plurality of databases;
wherein in the event that the database fails at being upgraded, another database of the cluster is available to be upgraded from the first version to the third version;
wherein in the event that each database of the cluster fails to be upgraded from the first version to the third version, a determination is made that the cluster is unable to be upgraded;
wherein each of the first version of the database, the third version of the database, and the second version of the database is associated with a fully migrated version of the database;
wherein for each translation path, the first version of the database, the second version of the database, and the third version of the database are different from each other; and
wherein for each translation path, the second version of the database is different from the second version of the database of another translation path.
2. The method as recited in claim 1 , wherein the first version is an existing version of the database.
3. The method as recited in claim 1 , wherein the third version is a new version of the database.
4. The method as recited in claim 1 , further including building a translation graph for selecting the translation path.
5. The method as recited in claim 1 , wherein a cluster of databases includes a plurality of versions of the database.
6. The method as recited in claim 1 , further including determining the first version of the database.
7. The method as recited in claim 1 , further including determining the database version of the first version of the database based on a key obtained by taking a hash of the database schema of the database in the first version.
8. The method as recited in claim 1 , wherein each object of the first version of the database includes a different number of members than each object of the third version of the database.
9. The method as recited in claim 1 , wherein each object of the first version of the database includes a different member from each object of the third version of the database.
10. The method as recited in claim 1 , wherein selecting the translation path is based on a hash value associated with the first version and a hash value associated with the third version.
11. The method as recited in claim 1 , wherein each converting step is lossless.
12. The method as recited in claim 1 , wherein the traversing step includes processing an XML representation of each of the converting steps.
13. The method as recited in claim 1 , wherein each converting step translates the database to a different version of the database.
14. The method as recited in claim 1 , wherein at least one of the translation paths includes at least four different versions of the database and at least three conversions to convert the database from the first version to the third version.
15. A system for converting a first version of a database to a third version, including:
a processor configured to:
select a translation path from a plurality of translation paths based on either a shortest path or a first path found, each translation path proceeding from the first version of the database to the third version of the database via a second version of the database; and
traverse the selected translation path comprising:
convert the first version of the database to the second version of the database; and
convert the second version of the database to the third version of the database,
wherein the database is part of a cluster including a plurality of databases;
wherein in the event that the database fails at being upgraded, another database of the cluster is available to be upgraded from the first version to the third version;
wherein in the event that each database of the cluster fails to be upgraded from the first version to the third version, a determination is made that the cluster is unable to be upgraded;
wherein each of the first version of the database, the third version of the database, and the second version of the database is associated with a fully migrated version of the database;
wherein for each translation path, the first version of the database, the second version of the database, and the third version of the database are different from each other; and
wherein for each translation path, the second version of the database is different from the second version of the database of another translation path; and
a memory that is coupled with the processor, wherein the memory provides the processor with instructions.
16. The system as recited in claim 15 , wherein the first version is an existing version of the database.
17. The system as recited in claim 15 , wherein the third version is a new version of the database.
18. The system as recited in claim 15 , wherein the processor is further configured to build a translation graph for selecting the translation path.
19. The system as recited in claim 15 , wherein a cluster of databases includes a plurality of versions of the database.
20. The system as recited in claim 15 , wherein the processor is configured to determining the database version of the first version of the database based on a key obtained by taking a hash of the database schema of the database in the first version.
21. The system as recited in claim 15 , wherein the processor is further configured to determine the first version of the database.
22. The system as recited in claim 15 , wherein each object of the first version of the database includes a different number of members than each object of the third version of the database.
23. The system as recited in claim 15 , wherein each object of the first version of the database includes a different member from each object of the third version of the database.
24. The system as recited in claim 15 , wherein each converting step translates the database to a different version of the database.
25. The system as recited in claim 15 , wherein selecting the translation path is based on a hash value associated with the first version and a hash value associated with the third version.
26. A computer program product for converting a first version of a database to a third version, the computer program product being embodied in a non-transitory computer readable storage device and comprising computer instructions for:
selecting a translation path from a plurality of translation paths based on either a shortest path or a first path found, each translation path proceeding from the first version of the database to the third version of the database via a second version of the database; and
traversing the selected translation path comprising:
converting the first version of the database to the second version of the database; and
converting the second version of the database to the third version of the database,
wherein the database is part of a cluster including a plurality of databases;
wherein in the event that the database fails at being upgraded, another database of the cluster is available to be upgraded from the first version to the third version;
wherein in the event that each database of the cluster fails to be upgraded from the first version to the third version, a determination is made that the cluster is unable to be upgraded;
wherein each of the first version of the database, the third version of the database, and the second version of the database is associated with a fully migrated version of the database;
wherein for each translation path, the first version of the database, the second version of the database, and the third version of the database are different from each other; and
wherein for each translation path, the second version of the database is different from the second version of the database of another translation path.