Object Conversion Summary

This section shows the object conversion Summary

Identified Objects

The count of all the top-level DDL objects (Table, View, Procedure, etc.) that the SnowConvert identified. If there were a parsing error on an object that made it unreconcilable, it wouldn't be an identified object.

CSV Associated field name

  • TotalIdentifiedObjects

Sample

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

-- Statements with parsing error
CREATE TABLE table2(
     column1 INT,
     column2 INT INT
);

CRATE TABLE table3(
     column1 INT
);

Expected Identified Objects: 2

Explanation: The table1 presented doesn't have a parsing error; the table2 even though it has a parsing error, the parser is still capable of recognizing the object as a table, so both are counted as an identified object; the table3 has a parsing error that makes it unreconcilable for the parser and, as a consequence, is not counted as an identified object.

Object Conversion Rate

The percentage of fully converted objects among the objects identified

Formula

(identify_objects_converted_succesfully / total_identify_objects) * 100

CSV Associated field name

  • ObjectConversionRate

Sample

IN -> Teradata_02.sql
CREATE TABLE table1(
     column1 INT,
     column2 INT 
);

CREATE VIEW view1 AS
SELECT orderkey
FROM orders;

CREATE TABLE table2(
     COLNAME VARCHAR(20)
)
ON COMMIT PRESERVE ROWS;

Expected Object Conversion Rate: 66.66%

Explanation: In this example we have 3 statements, all of them have been identified as an object, but just the table1, and the view1 have a 100% conversion rate. The table3 has an error warning meaning that the conversion of this table is not 100%, that's why just 2 of the 3 statements are counted as fully converted objects.

Fully Converted Objects

The number of identify objects that were converted successfully, meaning this objects have a 100% conversion rate.

CSV Associated field name

  • ObjectsSuccessfullyConverted

Sample

IN -> Teradata_03.sql
CREATE TABLE table1(
     column1 INT,
     column2 INT 
);

CREATE VIEW view1 AS
SELECT orderkey
FROM orders;

CREATE TABLE table2(
     COLNAME VARCHAR(20)
)
<