Performance Improvements in EDB Migration Toolkit 52.0.3
From the older version of EDB Postgres Migration Toolkit (MTK), it would take a while to finish the database migration because we can’t increase the value of fetch-Size option. Otherwise, it will result in Out of Memory error.
ITG, in partnership with EDB through Postgres Migration Toolkit, supported one of the biggest banks in the country to eliminate the risk of migration and improve the total migration process.
The ease of migration from legacy to open-source database helps the customer to adopt and migrate in a very fast-paced work environment.
The EDB Postgres Migration Toolkit (MTK) is a powerful command-line tool that offers granular control of the process of migrating database objects and data from other database management systems to EDB Postgres Advanced Server and PostgreSQL.
MTK supports migration of the following databases:
- Oracle® Database
- SQL Server
Migrating data from Oracle to Advanced Server using fetch-Size option:
Starting this release, the overall data migration time from Oracle to Advanced Server improved substantially while fixing the fetch-Size option related issue
Migrating table structure only:
runMTK.sh -sourcedbtype oracle -targetdbtype enterprisedb -schemaOnly -tables EMPLOYEES HRM
Migrating data using -fetchSize option (with different values):
runMTK.sh -sourcedbtype oracle -targetdbtype enterprisedb -dataOnly -fetchSize 10 -fastCopy -tables EMPLOYEES HRM
Fast Migration Process
Using JDBC’s default fetch-Size (Value for fetch-Size option is not specified):
While running MTK, if no value for fetch-Size is specified, then MTK uses default JDBC fetch-Size (10, in case of Oracle JDBC) and migrating hundred thousand rows takes around 40 minutes.
Improve Performance through fetch-Size option
After using the appropriate fetch-Size option, the performance has improved by 98% on average. Note: You may not see further significant improvement post a certain fetch-Size value.