SnowConvert: Teradata Conversion Settings¶

General Result Settings¶

1. Comment objects with missing dependencies: Flag to indicate if the user wants to comment on nodes that have missing dependencies.

2. Disable EWI comments generation (errors, warnings and issues): Flag to indicate whether EWIs comments (Errors, Warnings, and Issues) will not be generated on the converted code. The default is false

3. Generate XML-tags for SQL statements in Stored Procedures: Flag to indicate whether the SQL statements SELECT, INSERT, CREATE, DELETE, UPDATE, DROP, MERGE in Stored Procedures will be tagged on the converted code. This feature is used for easy statement identification on the migrated code. Wrapping these statements within these XML-like tags allows for other programs to quickly find and extract them. The decorated code looks like this:

   //<SQL_DELETE
   EXEC(DELETE FROM SB_EDP_SANDBOX_LAB.PUBLIC.USER_LIST,[])
   //SQL_DELETE!>
   

   Copy

4. Separate Period Data-type definitions and usages into begin and end Data-Time fields: This flag is used to indicate that the tool should migrate any use of the PERIOD datatype as two separate DATETIME fields that will hold the original period begin and end values, anytime a period field or function is migrated using this flag SSC-EWI-TD0053 will be added to warn about this change.

   Input Code:

   CREATE TABLE myTable(
      col1 PERIOD(DATE),
      col2 VARCHAR(50),
      col3 PERIOD(TIMESTAMP)
   );
   

   Copy

   Output Code:

   CREATE OR REPLACE TABLE myTable (
      col1 VARCHAR(24) !!!RESOLVE EWI!!! /*** SSC-EWI-TD0053 - SNOWFLAKE DOES NOT SUPPORT THE PERIOD DATATYPE, ALL PERIODS ARE HANDLED AS VARCHAR INSTEAD ***/!!!,
      col2 VARCHAR(50),
      col3 VARCHAR(58) !!!RESOLVE EWI!!! /*** SSC-EWI-TD0053 - SNOWFLAKE DOES NOT SUPPORT THE PERIOD DATATYPE, ALL PERIODS ARE HANDLED AS VARCHAR INSTEAD ***/!!!
   )
   COMMENT = '{"origin":"sf_sc","name":"snowconvert","version":{"major":1, "minor":0},{"attributes":{"component":"teradata"}}'
   ;
   

   Copy

5. Set encoding of the input files: The encoding code page number is used for parsing the source files. We only accept encodings supported by .NET Core (https://docs.microsoft.com/en-us/dotnet/api/system.text.encoding?view=net-5.0#list-of-encodings). Here are the ones supported at the moment:

6. Use COLLATE for Case Specification: This flag indicates whether to use COLLATE or UPPER to preserve Case Specification functionality, e.g. CASESPECIFIC or NOT CASESPECIFIC. By default, it is turned off, meaning that the UPPER function will be used to emulate case insensitivity (NOT CASESPECIFIC). To learn more about how Case Specification is handled by SnowConvert check here.

Session Mode Settings¶

This settings sub-page is used to indicate the Session Mode of the input code.

SnowConvert handles Teradata code in both TERA and ANSI modes. Currently, this is limited to the default case specification of character data and how it affects comparisons. By default, the Session Mode is TERA.

You can learn more about how SnowConvert handles and converts code depending on the session mode, check here.