Comment on page
Welcome to Snowflake SnowConvert for Teradata. Let us be your guide on the road to a successful migration.
Specifically, SnowConvert for Teradata performs the following conversions:
SnowConvert understands the Teradata source code and converts the Data Definition Language (DDL), Data Manipulation Language (DML), and functions in the source code to the corresponding SQL in the target: Snowflake. SnowConvert can migrate the source code in any of these three extensions .sql, .dml, ddl
Basic Teradata Query (BTEQ) is Teradata's proprietary scripting language. All BTEQ script files will be converted to Python scripts. A helper class will be called from the converted scripts to create the functional equivalence between the source and the target. More information about the Python Helpers can be found on our Translation Reference page. BTEQ can be batch run from outside the Snowflake environment. Learn more about how you can connect Python scripts directly to Snowflake.
BTEQ files are also the foundation for multiple other proprietary data types that Teradata has created:
Each one of these file types are extensions of BTEQ. SnowConvert translates each one of these file types to Python.
Each of these conversions are optimized to give you the most functionally equivalent output ready for use in Snowflake. For more information on the power of the kind of conversion SnowConvert can provide, you can learn more about our tool by visiting our complete SQL reference guide.
Before we get lost in the magic of these code conversions, here are a few terms/definitions so you know what we mean when we start dropping them all over the documentation:
- SQL (Structured Query Language): the standard language for storing, manipulating, and retrieving data in most modern database architectures.
- BTEQ (Batch Teradata Query): BTEQ was the first utility and query tool for Teradata.
- TPT (Teradata Parallel Transporter): TPT is a new generation utility tool that aims to create a one-stop tool for all the activities related to loading and exporting data from/to Teradata databases.
- SnowConvert: the software that converts securely and automatically your Teradata files to the Snowflake cloud data platform.
- Conversion rule or transformation rule: rules that allow SnowConvert to convert from a portion of source code to the expected target code.
- Parse: parse or parsing is an initial process done by SnowConvert to understand the source code and build up an internal data structure to process the conversion rules.
On the next few pages, you'll learn more about the kind of conversions that SnowConvert for Teradata is capable of. If you're ready to get started, visit the Getting Started page in this documentation. If you're interested in getting more information about SnowConvert in general, visit our SnowConvert for Teradata information page.
Teradata SQL Statement
-- CREATE TABLE DDL
CREATE SET TABLE TABLE1
NO BEFORE JOURNAL,
NO AFTER JOURNAL,
CHECKSUM = DEFAULT,
COL1 VARCHAR(15) CHARACTER SET LATIN NOT CASESPECIFIC,
Col2 BYTEINT CHECK ( CurrentFlag IN (0 ,1 ) ) NOT NULL,
COL3 DATE FORMAT 'yyyy-mm-dd',
COL7 INTEGER NOT NULL COMPRESS (1 ,2 ,3 ,4),
COL8 INTERVAL HOUR(2) TO MINUTE
-- REPLACE VIEW DDL
REPLACE VIEW VIEW1 AS
SELECT * FROM TABLE1
SELECT MAX(COL1) FROM TABLE1;
The Converted Snowflake SQL Code:
-- Snowflake converted SQL
CREATE TABLE PUBLIC. TABLE1
COL1 VARCHAR(15) COLLATE 'en-ci',
Col2 BYTEINT NOT NULL,
COL4 BINARY /**** WARNING: Column converted from BLOB data type ****/,
COL7 INTEGER NOT NULL,
COL8 VARCHAR (20) COMMENT 'INTERVAL HOUR(2) TO MINUTE' /**** WARNING: INTERVAL DATA TYPE "INTERVAL HOUR(2) TO MINUTE" CONVERTED TO VARCHAR ****/
CREATE OR REPLACE VIEW PUBLIC. VIEW1
SELECT * FROM PUBLIC. TABLE1
SELECT MAX(COL1) FROM PUBLIC. TABLE1 ;
In this converted SQL you will notice that we are converting many things such as:
PUBLICSchema by default for all the Table and view names if the user doesn't specify one (see how to specify a Schema).
CREATE SET TABLEto
CREATE OR REPLACE VIEW
- Data Types:
- Data Type Attributes:
- Removing pieces of the Teradata SQL that are not necessary in Snowflake due to Snowflake's architecture such as
NO BEFORE JOURNAL,
NO AFTER JOURNAL,