Overall Conversion Summary

This section shows the overall conversion summary

Total Files

Represents the number of files discovered in the input address and that were successfully migrated by SnowConvert.

CSV Associated field name

  • TotalFiles

Sample

input_folder
   ├> sql_file.sql
   ├> notes.txt
   └> views.csv

Expected Total Files: 1

Explanation: With the previous sample, we will only have the SQL file as valid for migration, as the other two files have an extension that SnowConvert cannot recognize.

SQL Files

This field applies only to Teradata reports.

This is the number of files detected in the input folder that have an extension of .sql, .ddl, or .dml.

CSV Associated field name

  • SqlFileCount

Sample

input_folder
    ├> ddl_file.ddl
    ├> dml_file.dml
    ├> sql_file.sql
    ├> other_file.ignore
    └> bteq_file.bteq

Expected SQL Files: 3

Explanation: In this case, the 3 files with extensions DDL, DML, and SQL are recognized as SQL Files. Other extensions are not counted for SQL Files. Teradata script files are not counted for SQL files, those are counted for Script files.

Script Files

This field applies only to Teradata reports.

This is the number of files in the input folder that are of the following type:

  • BTEQ: .bteq, .btq

  • FastLoad: .fload, .fl

  • MultiLoad: .mload, .mld, ml

  • TPump: .tpump, .tp

  • TPT: .tpt

CSV Associated field name

  • ScriptFileCount

Sample

input_folder
    ├> bteq_file.bteq
    ├> btq_file.btq
    ├> fload_file.fload
    ├> mload_file.mload
    ├> sql_file.sql
    ├> tpt_file.tpt
    └> tpump_file.tpump

Expected Script Files: 6

Explanation: In this case, the 6 files with extensions with Script file extensions are recognized as Script Files. The 2 extensions for BTEQ files previously mentioned are counted but the SQL file is not counted because it is a SQL File.

Total Files Not Generated

Represents the number of files found in the input address that, because of a failure in SnowConvert, failed to generate the migrated output file.

CSV Associated field name

  • TotalFilesNotGenerated

Sample

input_folder
   ├> input1.sql
   ├> input2.sql
   └> input3.sql

Expected Total File Not Generated: 1

Explanation:

Conversion Speed

Represents the number of lines processed per second during the migration.

Formula

total_lines_of_code / conversion_time

CSV Associated field name

  • ConversionSpeed

Sample

CREATE TABLE table1(
     column1 INT,
     column2 INT
     column3 INT 
);

CREATE VIEW view1 AS
SELECT orderkey
FROM orders;

Expected Conversion Speed: 4 lines/sec

Explanation: Let's say that the example execution time was 2 seconds, taking into account that the number of lines is 8. Applying the formula 8/2 = 4, so the Converting Speed is 4 lines per sec.

Conversion Time

Represents the duration of SnowConvert's migration.

CSV Associated field name

  • ElapsedTime

Total Conversion Errors

The total count of conversion errors that occurred during the conversion process. This type of error could be related to file I/O, memory management, or any abnormal situation that cannot be handled by SnowConvert. These are unhandled code exceptions and are considered critical issues.

CSV Associated field name

  • TotalConversionErrors

Total Parsing Errors

The total count of parsing errors that occurred during the code analysis process. A parsing error occurs when the parser (the component that reads the source code files) encounters something unexpected. This usually means a syntax error, which refers to a code element in the file that did not match the SQL grammar specification that the parser was expecting. In other cases, these errors can also occur because the parser is not yet ready to support a specific grammar. Parsing errors are also considered critical issues. If this number is high in relation to the migration workload size, input code revision is advised.

CSV Associated field name

  • TotalParsingErrors

Sample

IN -> Teradata_01.sql
-- Statement without parsing error
CREATE TABLE table1(
     column1 INT,
     column2 INT 
);

-- Statements with parsing error
CRATE TABLE table2(
     column1 INT
);

CREATE VIEW view1 AS
SELECT orderkey
FROM FROM orders;