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.
-- Statement without parsing errorCREATE OR REPLACETABLEtable1 ( column1 INT, column2 INT)COMMENT = '{"origin":"sf_sc","name":"snowconvert","version":{"major":1, "minor":0},"attributes":{"component":"teradata"}}'
;-- Statements with parsing errorCREATE OR REPLACETABLEtable2 ( column1 INT-- ,-- ** SSC-EWI-0001 - UNRECOGNIZED TOKEN ON LINE '10' COLUMN '6' OF THE SOURCE CODE STARTING AT 'column2'. EXPECTED 'Column Definition' GRAMMAR. LAST MATCHING TOKEN WAS 'INT' ON LINE '10' COLUMN '14'. CODE '15'. **
-- column2 INT INT)COMMENT = '{"origin":"sf_sc","name":"snowconvert","version":{"major":1, "minor":0},"attributes":{"component":"teradata"}}'
;-- ** SSC-EWI-0001 - UNRECOGNIZED TOKEN ON LINE '13' COLUMN '1' OF THE SOURCE CODE STARTING AT 'CRATE'. EXPECTED 'STATEMENT' GRAMMAR. LAST MATCHING TOKEN WAS 'CRATE' ON LINE '13' COLUMN '1'. CODE '81'. **
--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