Migrating SQL Server to Aurora with Minimal Code Changes

SAA-C03 By islever Editorial Last updated

Determine appropriate data security controls.

Short answer

BC Enable Babelfish on Aurora PostgreSQL to accept SQL Server queries and use AWS SCT and DMS to migrate the schema and data.

Question

A company uses a Microsoft SQL Server database. The company's applications are connected to the database. The company wants to migrate to an Amazon Aurora PostgreSQL database with minimal changes to the application code. Which combination of steps will meet these requirements? (Choose two.)
  1. Use the AWS Schema Conversion Tool (AWS SCT) to rewrite the SQL queries in the applications.
  2. Enable Babelfish on Aurora PostgreSQL to run the SQL queries from the applications. Correct Answer
  3. Migrate the database schema and data by using the AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS). Correct Answer
  4. Use Amazon RDS Proxy to connect the applications to Aurora PostgreSQL.
  5. Use AWS Database Migration Service (AWS DMS) to rewrite the SQL queries in the applications.

Key Takeaways

The question tests the ability to combine schema migration with protocol compatibility; the trap is assuming code rewriting is required or confusing DMS capabilities.

This guide explains how to migrate a Microsoft SQL Server database to Amazon Aurora PostgreSQL while keeping application code changes minimal using AWS Database Migration Service, AWS Schema Conversion Tool, and Babelfish.

Common mistake: Learners often select options involving 'rewriting' queries (A or E), not realizing that tools like DMS do not rewrite application code and Babelfish handles protocol translation instead.

Expert Analysis

Why the Answer Is Correct

To achieve minimal changes to application code when moving from SQL Server to Aurora PostgreSQL, you must address both data migration and query compatibility. Option C uses AWS SCT to convert the schema and AWS DMS to migrate data, which is the standard approach for moving the backend structure. Option B enables Babelfish on Aurora PostgreSQL, a feature specifically designed to allow applications written for Microsoft SQL Server to connect to Aurora using the T-SQL language and SQL Server protocol without modification. Together, they solve the structural and connectivity gaps.

Why the Other Options Are Wrong

Options A and E are incorrect because neither AWS SCT nor AWS DMS rewrites SQL queries embedded in application source code; SCT converts schemas/stored procedures, and DMS migrates data. Option D, Amazon RDS Proxy, helps manage database connections and scalability but does not translate SQL dialects or assist in migration, so it fails the 'minimal code change' requirement regarding the database engine switch.

Community Comment Notes

The community consensus strongly supports BC. As sandordini noted, Babelfish allows Aurora to understand SQL Server commands, while SCT and DMS handle the conversion and migration naturally. KennethNg923 pointed out that since A and E involve rewriting queries, they are invalid, leaving B and C as the only logical pair. Scheldon confirmed that minimizing code changes necessitates Babelfish alongside the migration tools.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

When a question emphasizes 'minimal changes' or 'compatibility' during an engine migration, look for features that provide protocol-level emulation (like Babelfish) rather than code refactoring tools. Always pair data/schema migration tasks with their respective tools (SCT/DMS).

Frequently Asked Questions

Does AWS DMS rewrite application SQL code?

No. AWS DMS migrates data between heterogeneous databases but does not modify or rewrite the SQL queries inside your application code.

What is the role of Babelfish in this migration?

Babelfish allows Aurora PostgreSQL to accept connections and T-SQL queries from existing SQL Server applications, eliminating the need to rewrite application code.

More SAA-C03 FAQ →

Community Votes

BC
100%

100% of anonymous learners picked answer BC. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 5 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 5

  1. sandordini 👍 5
    B: Babelfish for Aurora PostgreSQL is a new capability for Amazon Aurora PostgreSQL-Compatible Edition that enables Aurora to understand commands from applications written for Microsoft SQL Server. C: Is just obvious: Use Data Migration Tool for the migration, Schema Conversion tool for the Schema conversion.
  2. pranavsharma1604 👍 4
    https://aws.amazon.com/rds/aurora/babelfish/
  3. Scheldon 👍 2
    AnswerBC DMS will allow for DATABASE migration and use AWS Schema Conversion Tool (AWS SCT) to create some or all of the target tables, indexes, views, triggers, and so on. https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html To minimalize amount of code which need to me changes we need to use babelfish https://aws.amazon.com/rds/aurora/babelfish/
  4. KennethNg923 👍 2
    DMS + SCT is correct, but " rewrite the SQL queries in the applications." is wrong so A + E are out. Then only left B + C -> DMS + SCT + Babekfish (for SQL Server)
  5. LeonSauveterre 👍 1
    A - AWS SCT does not directly rewrite SQL queries in the application code. This would require manual updates. B - Babelfish allows Aurora PostgreSQL to understand SQL Server’s native T-SQL language and protocol. C - Convert the schema & migrate the data effectively, good. D - Amazon RDS Proxy improves database scalability and availability (if the question mentions something like having trouble conneting during peek hours or whatnot then RDS Proxy is likely the answer) but does not address the compatibility issues between SQL Server and Aurora PostgreSQL. E - This is not enough. Refer to option C.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide