AWS Schema Conversion Tool Adds New Conversion Features

The
AWS Schema Conversion Tool (AWS SCT) makes heterogeneous database migrations predictable by automatically converting the source database schema and a majority of the database code objects, including views, stored procedures, and functions, to a format compatible with the target database. With the latest version of AWS SCT (build 624), you can now take advantage of the following enhanced conversion features:
 
  1. Support for orafce extension when migrating from Oracle to PostgreSQL:  The orafce extension in PostgreSQL implements a subset of Oracle PL/SQL subprograms and packages in PostgreSQL, making the conversion of programmable database objects a straightforward task and migrations to PostgreSQL faster and easier. The orafce extension is supported in both Aurora PostgreSQL-compatible edition and RDS for PostgreSQL. More details about orafce can be found here.
  2. SAP ASE as a source support:  You can now convert database objects from an SAP Adaptive Server Enterprise (ASE) database—formerly known as Sybase—using AWS SCT to Amazon Aurora (PostgreSQL and MySQL-compatible editions), RDS for MySQL and RDS for PostgreSQL.
  3. RDS for MariaDB 10.2 & 10.3 as a target support:  You can now convert database objects from Oracle, Microsoft SQL Server and Db2 LUW to RDS for MariaDB versions 10.2 and 10.3 using AWS SCT. This gives you another option to migrate from commercial databases to an open source database in the cloud.
After converting your database schema and code objects using SCT, you can use  the
AWS Database Migration Service to migrate data from the source database to the target database to complete your migration projects.