AWS Schema Conversion Tool features

[Aleksandr Teterin]

Practice exam Question
A leading media company has recently adopted a hybrid cloud architecture which requires them to migrate their application servers and databases in AWS. One of their applications requires a heterogeneous database migration in which you need to transform your on-premises Oracle database to PostgreSQL in AWS. This entails a schema and code transformation before the proper data migration starts.

Correct answer
First, use the AWS Schema Conversion Tool to convert the source schema and application code to match that of the target database, and then use the AWS Database Migration Service to migrate data from the source database to the target database.

Note
AWS Schema Conversion Tool features are focused on database-related objects such as schema, stored procedures, and triggers …. It is not designed to convert full application code (e.g., Java-based code) that interacts with the database. Application code may use source database-specific features that are not available in the target database, requiring manual adjustments.

Shall the mention of “application code” be removed from the answer?

[Neil-TutorialsDojo]

Hello Aleksandr Teterin,

Good day!

Thank you for your thoughtful feedback and for pointing out the AWS Schema Conversion Tool (SCT) capabilities. You raise an excellent point about its primary focus on database objects.

To clarify, mentioning “application code” refers to database-related code within applications. SCT can assist in converting SQL-related code embedded in languages like C++, C#, Java, and others that use database interface code. However, SCT is indeed not designed to transform entire applications or non-database-related logic.

We appreciate your attention to this detail and will consider rephrasing the item to clarify this distinction.

Thank you once again for your valuable feedback.

Regards,

Neil @ Tutorials Dojo