Converting Teradata BTEQ scripts to Amazon Redshift RSQL with AWS SCT - AWS Schema Conversion Tool
Adding BTEQ scripts to your AWS SCT projectConfiguring substitution variables in BTEQ scriptsConverting BTEQ scriptsManaging BTEQ scriptsCreating a BTEQ script conversion assessment reportEditing and saving your converted BTEQ scripts

Converting Teradata BTEQ scripts to Amazon Redshift RSQL with AWS SCT

You can use the AWS Schema Conversion Tool (AWS SCT) to convert Teradata Basic Teradata Query (BTEQ) scripts to Amazon Redshift RSQL.

The following architecture diagram shows the database migration project that includes the conversion of extract, transform, and load (ETL) scripts to Amazon Redshift RSQL.

A diagram showing the conversion of ETL scripts to RSQL.

Adding BTEQ scripts to your AWS SCT project

You can add multiple scripts to a single AWS SCT project.

To add a BTEQ script to your AWS SCT project

  1. Create a new project in AWS SCT or open an existing project. For more information, see Starting and managing Projects in AWS SCT.

  2. Choose Add source from the menu, and then choose Teradata to add your source database to the project. For more information, see Teradata databases.

  3. Choose Add target from the menu to add a target Amazon Redshift database to your AWS SCT project.

    You can use a virtual Amazon Redshift target database platform. For more information, see Mapping to virtual targets in the AWS Schema Conversion Tool.

  4. Create a new mapping rule that includes your source Teradata database and your Amazon Redshift target. For more information, see Mapping new data types in the AWS Schema Conversion Tool.

  5. On the View menu, choose Main view.

  6. In the left panel, expand the Scripts node.

  7. Choose BTEQ scripts, open the context (right-click) menu, and then choose Load scripts.

  8. Enter the location of the source code for your Teradata BTEQ scripts and choose Select folder.

    AWS SCT displays the Load scripts window.

  9. Do one of the following:

    1. If your Teradata BTEQ scripts don't include the substitution variables, choose No substitution variables, and then choose OK to add scripts to your AWS SCT project.

    2. If your Teradata BTEQ scripts include the substitution variables, configure the substitution variables. For more information, see Configuring substitution variables in BTEQ scripts.

Configuring substitution variables in BTEQ scripts with AWS SCT

Your Teradata BTEQ scripts can include substitution variables. For example, you can use one BTEQ script with substitution variables to run the same set of commands on multiple database environments. You can use AWS SCT to configure substitution variables in your BTEQ scripts.

Before you run a BTEQ script with substitution variables, make sure to assign the values for all variables. To do this, you can use other tools or applications such as a Bash script, UC4 (Automic), and so on. AWS SCT can resolve and convert substitution variables only after you assign their values.

To configure substitution variables in your BTEQ script

  1. Add your BTEQ scripts to your AWS SCT project. For more information, see Adding BTEQ scripts to your AWS SCT project.

    When you add your scripts, choose Substitution variables are used.

  2. For Define variable format, enter a regular expression that matches all substitution variables in your script.

    For example, if the names of your substitution variables start with ${ and end with }, use the \$\{\w+\} regular expression. To match substitution variables that start either with a dollar sign or a percent sign, use the \$\w+|\%\w+ regular expression.

    Regular expressions in AWS SCT conform to the Java regular expression syntax. For more information, see java.util.regex Class Pattern in the Java documentation.

  3. Choose OK to load scripts to your AWS SCT project, and then choose OK to close the Load scripts window.

  4. Choose Variables to view all discovered substitution variables and their values.

  5. For Value, enter the value for the substitution variable.

Converting Teradata BTEQ scripts to Amazon Redshift RSQL with AWS SCT

Following, find how to convert BTEQ ETL scripts to Amazon Redshift RSQL using AWS SCT.

To convert a Teradata BTEQ script to Amazon Redshift RSQL

  1. Add your BTEQ scripts to your AWS SCT project. For more information, see Adding BTEQ scripts to your AWS SCT project.

  2. Configure the substitution variables. For more information, see Configuring substitution variables in BTEQ scripts.

  3. In the left panel, expand the Scripts node.

  4. Do one of the following:

    • To convert a single BTEQ script, expand the BTEQ scripts node, choose the script to convert, and then choose Convert to RSQL from the context (right-click) menu.

    • To covert multiple scripts, make sure that you select all scripts to convert. Then choose BTEQ scripts, open the context (right-click) menu, and then choose Convert to RSQL under Convert script.

    AWS SCT converts all your selected Teradata BTEQ scripts to a format compatible with Amazon Redshift RSQL. Find your converted scripts in the Scripts node in the target database panel.

  5. Edit your converted Amazon Redshift RSQL scripts, or save them. For more information, see Editing and saving your converted BTEQ scripts.

Managing BTEQ scripts with AWS SCT

You can add multiple BTEQ scripts or remove a BTEQ script from your AWS SCT project.

To add an additional BTEQ script to your AWS SCT project

  1. Expand the Scripts node in the left panel.

  2. Choose the BTEQ scripts node, and open the context (right-click) menu.

  3. Choose Load scripts.

  4. Enter the information that is required to add a new BTEQ script and configure substitution variables. For more information, see Adding BTEQ scripts to your AWS SCT project and Configuring substitution variables in BTEQ scripts.

To remove a BTEQ script from your AWS SCT project

  1. Expand the BTEQ scripts node under Scripts in the left panel.

  2. Choose the script to remove, and open the context (right-click) menu.

  3. Choose Delete script.

Creating a BTEQ script conversion assessment report with AWS SCT

A BTEQ script conversion assessment report provides information about converting the BTEQ commands and SQL statements from your BTEQ scripts to a format compatible with Amazon Redshift RSQL. The assessment report includes action items for BTEQ commands and SQL statements that AWS SCT can't convert.

To create a BTEQ script conversion assessment report

  1. Expand the BTEQ scripts node under Scripts in the left panel.

  2. Choose the script to convert, and open the context (right-click) menu.

  3. Choose Conversion to RSQL under Create report.

  4. View the Summary tab. The Summary tab displays the executive summary information from the BTEQ script assessment report. It includes conversion results for all BTEQ commands and SQL statements from your BTEQ scripts.

  5. (Optional) Save a local copy of the BTEQ script conversion assessment report as either a PDF file or a comma-separated values (CSV) file:

    • To save the BTEQ script conversion assessment report as a PDF file, choose Save to PDF at upper right.

      The PDF file contains the executive summary, action items, and recommendations for scripts conversion.

    • To save the BTEQ script conversion assessment report as a CSV file, choose Save to CSV at upper right.

      The CSV file contains action items, recommended actions, and an estimated complexity of manual effort required to convert the scripts.

  6. Choose the Action items tab. This tab contains a list of items that require manual conversion to Amazon Redshift RSQL. When you choose an action item from the list, AWS SCT highlights the item from your source BTEQ script that the action item applies to.

Editing and saving your converted BTEQ scripts with AWS SCT

You can edit your converted scripts in the lower panel of your AWS SCT project. AWS SCT stores the edited script as part of your project.

To save your converted scripts

  1. Expand the RSQL scripts node under Scripts in the target database panel.

  2. Choose your converted script, open the context (right-click) menu, and choose Save script.

  3. Enter the path to the folder to save the converted script and choose Save.

    AWS SCT saves the converted script to a file and opens this file.