Data migration
View Patent ↗Various embodiments herein each include at least one of systems, methods, and software for data migration, such as when migrating a database from one form to a next and as may be performed at a time of software system version migration. One example embodiment, in the form of a method, includes loading a database migration script that includes a prior class from a software system prior to an upgrade of the software system and a new class from the software system after the upgrade to the software system. The method proceeds by then calling methods of the prior class to copy database data from database tables impacted by the database migration script to a memory device and executing the database migration script. The method then calls methods of the new class to copy the database data from the memory device back to the database.
1. A method comprising:
loading a database migration script that includes a prior class from a software system prior to an upgrade of the software system and a new class from the software system after the upgrade to the software system;
calling methods of the prior class to copy database data from database tables impacted by the database migration script to a memory device wherein the called methods of the prior class perform at least one of copying, manipulating, and transforming the data;
executing the database migration script; and
calling methods of the new class to copy the database data from the memory device back to the database wherein the called methods of the new class perform at least one of copying, manipulating, and transforming the data.
2. The method of claim 1 , wherein:
the prior class is loaded into memory for execution of the methods thereof prior to the methods being called and the prior class is then unloaded after copying of the database data to the memory device; and
the new class is loaded into memory for execution of the methods thereof subsequent to the executing of the database migration script and prior to the methods being called.
3. The method of claim 1 , wherein the database migration script, the prior class, and the new class are bundled as a database migration plan that is executable by a database migration tool.
4. The method of claim 3 , wherein the database migration tool provides a computing environment within which the prior class and the new class are executable.
5. The method of claim 4 , wherein a database migration tool s available for each of a plurality of computing platforms, each of which is able to execute the same database migration plan.
6. The method of claim 4 , further comprising:
stopping execution of the software system prior to execution of the database migration plan;
issuing a database migration tool command to begin execution of the database migration plan; and
restarting execution of the software system.
7. The method of claim 6 , further comprising:
modifying the software system that executes against data stored in the database.
8. The method of claim 6 , further comprising:
modifying the software system that executes against data stored in the database.
9. A method comprising:
copying data from a database to a memory device by calling a method of a first, prior version of a class of a prior version of a software application, wherein the called method of the first, prior class perform at least one of copying, manipulating, and transforming the data;
executing a database change script that changes a database table from which the data was copied, the database table changes made from a form of the database table as utilized by the prior version of the application to a new version of the software application; and
copying data back to the database from the memory device by calling a method of a second, new version of the class of the new version of the software application, wherein the called method of the second, new class perform at least one of copying, manipulating, and transforming the data.
10. The method of claim 9 , wherein:
the first, prior and second, new versions of the class are classes of the software application that executes against the data copied from and to the database;
the first, prior version of the class is tailored to the database prior to changes being made to the database table through the execution of the database change script; and
the second, new version of the class is tailored to the database after changes are made to the database table through the execution of the database change script.
11. The method of claim 10 , wherein:
the first, prior version of the class is loaded into memory for execution of the methods thereof prior to the methods being called and the first class is then unloaded after copying of the database data to the memory device; and
the second, new version of the class is loaded into memory for execution of the methods thereof subsequent to the executing of the database change script and prior to the methods of the second, new version of the class being called.
12. The method of claim 9 , wherein the database change script, the first, prior version of the class, and the second, new version of the class are bundled as a database change plan that is executable by a database change tool.
13. The method of claim 12 , wherein the database change tool provides a computing environment within which the first, prior version of the class and the second, new version of the class are executable.
14. The method of claim 13 , wherein a database change tool is available for each of a plurality of computing platforms, each of which is able to execute the same database change plan.
15. The method of claim 13 , further comprising:
stopping execution of the software system prior to execution of the database change plan;
issuing a database change tool command to begin execution of the database change plan; and
restarting execution of the software system.
16. A system comprising:
a processor, a memory device, an ancillary memory device, and instructions stored on the at least one memory device that are executable by the processor to perform data processing activities, the data processing activities comprising:
copying data from a database to the ancillary memory device by calling a method of a first, prior version of a class of a prior version of a software application, wherein the called method of the first, prior class perform at least one of copying, manipulating, and transforming the data;
executing a database change script that changes a database table from which the data was copied, the database table changes made from a form of the database table as utilized by the prior version of the application to a new version of the software application; and
copying data back to the database from the ancillary memory device by calling a method of a second version of the class of the new version of the software application, wherein the called method of the second, new class perform at least one of copying, manipulating, and transforming the data.
17. The system of claim 16 , wherein the ancillary memory device is a data storage device of the system.
18. The system of claim 16 wherein:
the first, prior and second, new versions of the class are classes of the software application that executes against the data copied from and to the database;
the first, prior version of the class is tailored to the database prior to changes being made to the database table through the execution of the database change script; and
the second, new version of the class is tailored to the database after changes are made to the database table through the execution of the database change script.
19. The system of claim 18 , wherein:
the first, prior version of the class is loaded into memory for execution of the methods thereof prior to the methods being called and the first class is then unloaded after copying of the database data to the memory device; and
the second, new version of the class is loaded into memory for execution of the methods thereof subsequent to the executing of the database change script and prior to the methods of the second version of the class being called.
20. The system of claim 16 , wherein:
the database change script, the first, prior version of the class, and the second, new version of the class are bundled as a database change plan that is executable by a database change tool; and
the database change tool provides a computing environment within which the first, prior version of the class and the second, new version of the class are executable.