Question

A retail company runs a 40 TB on-premises Teradata data warehouse that must be migrated to Amazon Redshift. The Teradata schema uses proprietary SQL dialects, stored procedures, and BTEQ scripts that are incompatible with Redshift. The company's data center has a 1 Gbps internet connection that is heavily utilized during business hours, and the migration must minimize disruption to ongoing analytics. Which combination of approaches BEST accomplishes the schema conversion and bulk data transfer?

Accepted Answer

Use the AWS Schema Conversion Tool (SCT) to convert the Teradata schema and code to Redshift-compatible objects, then use SCT data extraction agents to export data to AWS Snowball Edge devices for offline bulk transfer into Redshift.

Answer

Use AWS Database Migration Service (DMS) with a full-load task over the internet to migrate both the schema and the 40 TB of data directly into Redshift in a single operation.

Answer

Use AWS DataSync to copy the raw Teradata data files to Amazon S3, then run the COPY command to load them into Redshift, relying on native Redshift SQL to recreate stored procedures automatically.

Answer

Set up an AWS Direct Connect link to transfer the 40 TB over the network, then use DMS continuous replication to convert and migrate the Teradata schema, procedures, and data into Redshift.