DB Best has released a new version of Migration Platform, an all-around program for automating database migration processes. This newer 1.2 version improves error handling practices for Test Organizer by creating additional mapping rules for matching different error messages and codes. We have also added the partial data backup and restore functionality along with the capability to add and remove tables from existing datasets for the Data Store module. On top of that, we have enabled more options for command timeouts for the Data Comparison, Test Organizer, Data Store, and Data Migration modules. Be sure to check out our guides on using the core features of Migration Platform:
What’s new in the DB Best Migration Platform 1.2?
First off, in the Test Organizer module, users receive full control over error handling. It’s always important that both the Source and Target databases perform the same way, so users can now polish this practice if the test errors had similar causes. By using the new functionality, you can have previously failed tests added to exception and successfully pass. Depending on the default mapping rules, expected errors can be automatically passed if they have similar values. To apply the same behavior to not expected errors, a new mapping rule should be added manually.
To know more about errors handling procedures, please watch the following video:
Expected errors include more traditional errors that occur during the migration process. They usually include “cannot insert NULL”, “violates foreign key constraint”, “cannot upgrade to NULL”, and other scenarios. To enable automatic error handling, you should head over to the Main Menu in the upper left corner of the screen, then proceed to Project Settings > Test Organizer, and check the “Show the Advanced compare options” tab. It will create the Advanced compare options tab in your main Test Organizer field, where you can check the Override parent options and Compare error messages options and click on Save. After running your Test Suite, you will see that expected errors will pass and the result tab will show different errors from the Source and Target databases matching in the Exceptions field.
Not expected errors
Not expected errors include less traditional scenarios for errors such as CASE_NOT_FOUND, INVALID_CURSOR, and VALUE_ERROR. To enable custom behavior for such errors, you should first enable the Compare error messages option the same way as for expected errors. Then, head over to MAPPING > Add, and enter specific error codes or messages for both the Source and Target databases you encountered in the Results tab in your main Test Organizer field.
UPD: We improved the error handling menu in the latest Migration Platform 1.5 version. Check it out for more details.
For the Data Store module, we automated the extension packs installation process. Users no longer need to perform manual configuration — now it’s done by right-clicking on a schema and selecting the Install extension packs option. After installation, the schema will display a black check mark and the Packages list will contain installation packs.
To know more about the Data Store module improvements, please watch the following video:
Also, we enabled more options for Data Store, in the form of golden copy functionality for your data. Let’s say, your database has new tables you would like to backup. So, instead of creating numerous new datasets, users can now add tables from the metadata tree to existing datasets by right-clicking on desired tables and selecting the Add to Dataset option. By using this option, users can keep their actual data backed up in a single dataset and restore if needed.
What’s more, the new update provides users with a full grasp over datasets by selecting which tables will be backed up or restored. For tracking the backup and restore progress, there is the State bar that will show completion status once the process is finished. The remove feature has also been added for separate tables. Now, instead of removing and creating whole new datasets, users can remove separate objects that no longer need to be backed up or restored.
Command timeout in modules
With the new release, each of the Data Comparison, Test Organizer, Data Store, and Data Migration modules received their own command timeout settings. It lets users specify the exact time for a command to complete for both the Source and Target databases. For each module, these timeouts have a purpose:
- Data Comparison timeouts show the time it takes comparison reports to be checked for a database.
- Test Organizer timeouts show the time it takes the SQL block, pre scripts, and post script to complete.
- Data Store timeouts show the time it takes backup and restore processes to complete.
- Data Migration timeouts show the time it takes a single database request to complete.
Free trial download
You can download a free trial version of the DB Best Migration Platform from the official product page. This version works for a limited period. However, if you want to continue using this fully automated database migration product, please drop us a line.