Replacing Oracle with Postgres: How To Successfully Migrate Your Legacy Databases

Comparing the migration techniques

Take for example one of our large media customers: The company migrated its Oracle database containing 10,938 database objects (tables, stored procedures, packages, etc.) in 35 person days, including data transfer and testing, as 91% of all the objects were supported by EDB’s native compatibility. Only two packages, which included approximately 9% of the code, needed to be rearchitected for compatibility with EDB Postgres Advanced Server.

In the same application, only the storage objects (tables and views) and some functions were open source Postgres compatible using the translation approach with ORA2PG. The rearchitecting approach for 65% of the code was estimated to be between 1.5 and 2 person years of effort.

First Name *

Last Name *

Email *

Phone Number *

Company Name *

Job Title *

Address *

City *

State or Province *

Zip or Postal Code *

Country *

Company Size *

Industry *

What budget have you allocated for database management solutions or open-source database modernization in the upcoming quarter? *

Who is responsible for making decisions regarding database technology and infrastructure within your organization? *

When are you planning to implement new database technologies or upgrade your current system? *

What challenges are you currently facing with your database management or migration from legacy systems to Postgres? *

If you engage with the content, Software Insider will share your data with EDB. For details on their information practices and how to unsubscribe, see their Privacy Statement. You can unsubscribe at any time.

FILL THE FORM BELOW

You have been directed to this site by Software Insider. For more details on our information practices, please see our Privacy Policy, and by accessing this content you agree to our Terms of Use. You can unsubscribe at any time.

Replacing Oracle with Postgres: How To Successfully Migrate Your Legacy Databases