Jun 53 min read

Achieve a Truly Open-Source PostgreSQL Migration with AWS Schema Conversion Tool - aws_oracle_ext - Part 1

Updated: Jul 16

Introduction

Migrating to PostgreSQL from databases like Oracle or MSSQL can be a daunting task, incurring significant time and cost. The majority of this effort is spent on code conversion and ensuring its functionality. But what if you migrated to a database that's supposedly PostgreSQL-compatible, only to discover later it's not truly open source and still locks you in?

For AWS users migrating to RDS or Amazon Aurora, the AWS Schema Conversion Tool might seem like a one stop shop solution for code conversion. However, beware! It relies on extension packs – essentially proprietary code that mimics your old database's functionality, trapping you in new vendor lock-in.

For more insight, please do check out our blog "Breaking Free: Transitioning Your Database Away from AWS Extension Pack to Truly Open" and our open source extensions pack detection tool.

Solution to reduce dependency with AWS Schema Conversion Tool Extension Pack.

Extensions pack inclusion in your database can introduce uncertainty with performance, harder to maintain and upgrade.

PostgreSQL migrations should be driven by an approach that ensures the converted code is truly open and supported by community extensions. Our efforts should focus on transforming databases that is easier to maintain, upgrade, and performant for our application's current and future needs.

Let's explore option to enable migration to open-source PostgreSQL that will empower you with freedom, it allows to move seamlessly between any cloud platform without hidden restrictions.

SCTMigrator - Enablers to truly open source PostgreSQL.

Leveraging our experience migrating dozens of customers from Oracle and MSSQL, we've developed an automated solution that significantly reduces your reliance on AWS SCT extension packs. This empowers you to migrate to PostgreSQL using native options and orafce extensions for most functionalities previously achieved through extension pack code embedded in the AWS Schema Conversion Tool output.

Following conversion with the AWS Schema Conversion Tool, our solutions can help you replace unnecessary AWS SCT Extension Pack code with equivalent PostgreSQL native functionality within your database procedural code. Currently we are offering free trial with limited attempt that empowers AWS customers to eliminate hidden vendor lock-in with extension pack and transform it to native alternatives.

Check out the video on how you can leverage our sct-migrator app to transform embedded AWS SCT Extension packs with PostgreSQL native alternative.

Ready to break free from vendor lock-in and achieve a truly open-source PostgreSQL migration on AWS? DataCloudGaze Consulting is your expert partner.

Leveraging our experience migrating dozens of customers and our innovative SCT-Migrator tool, we'll help you ditch AWS SCT extension packs and migrate to a performant, future-proof PostgreSQL compatible code.

Mail to :- contact@datacloudgaze.com

Talk to Us :- Book a meeting

Read further for more insight on how to reduce extension pack dependency.

Orafce Extension to our rescue for Oracle as Source.

Orafce Extensions provide functions and operators that emulate a subset of functions and packages from the Oracle RDBMS. It is available as supported Extensions in many Cloud managed instance on AWS, Azure, GCP and more.

Below is the mapping view between Extension Pack Schema - AWS_ORACLE_EXT and its alternative with orafce functions for most common Oracle functions.

AWS Extension Pack - aws_oracle_ext vs orafce

PL/SQL's DBMS_% packages require special attention during Oracle to PostgreSQL migration. Sharing AWS_ORACLE_EXT functions to PostgreSQL-compatible orafce alternatives for DBMS_% packages.

AWS SCT integration with Orafce Extensions.

The AWS Schema Conversion Tool allows configuration to use orafce-based wrapper functions instead of the AWS SCT Extension Pack for handling Oracle common functions and DBMS_% packages.

AWS SCT - Enabling Orafce Extension — AWS SCT - Using orafce implementation

Our analysis still shows limitations with the AWS Schema Conversion Tool's ability to fully leverage orafce extensions during your PostgreSQL migration. To ensure a smooth transition, we recommend exploring alternative approaches based on the provided mapping.

Additionally, the AWS Schema Conversion Tool's reliance on proprietary AWS Extension Packs for advanced features like global variables and collection processing that will anyhow introduce vendor lock-in.