• Customer: Governmental service provider
  • Country: United States
  • Product Used: Ispirer Toolkit License
  • Source Technology: IBM DB2 LUW
  • Target Technology: EDB Postgres
  • Project Scope: 100,000 LOC
  • Project Duration: 2016-2017


Ispirer's customer is an american public corporation and independent unit of state government.


The customer approached Ispirer Systems with the challenge of implementation of PostgreSQL as the enterprise database platform. To achieve this aim they needed to transfer tables and data in multiple QA and production environments from DB2 LUW to EDB Postgres. Ispirer Toolkit has been chosen for this purpose.


During the Analysis Stage, the lspirer team examined whole of the customer’s source code. The Ispirer support team diligently and responsively supported the customer, helping them to make updates to the tool to meet specific requirements during the migration process.

During the Extension Stage, the functionality of the toolkit was significantly improved due to added extensions. For instance, the solution that emulates MONTHS_BETWEEN function in PostgreSQL has been developed specifically for this project. Moreover, support of TABLESPACE conversion in tables and support of Common Table Expressions in views has been added.

The customized Ispirer SQLWays Wizard seamlessly handled the conversion of structures and data types of over 300 tables from DB2 to EDB Postgres semantics.

Benefits Derived from Conversion

The whole database migration project was successfully accomplished in due time. Both data and table conversion processes went smoothly. The tool helped the client to migrate over 5 terabytes of total data from IBM DB2 to a new EnterpriseDB (PostgreSQL) database in a timely, automated, and repeatable fashion.

In addition, the customer remained satisfied with the product choice and the results obtained. Its Chief Information Security Officer said: “Overall, we are very happy with the product's capabilities and will recommend this to any enterprise undertaking large scale database migration efforts.”