HTML Report

The HTML report provides a general overview of the results from the transformation. This documentation will provide a guide on how to read the report’s content.

This is a deprecated version of the SnowConvert documentation, please visit the official site HERE.

Header

• Run ID: Unique identifier for the report. It is also contained in the report’s name and matches the other reports' names as well.

• Date when the report was created.

• SnowConvert version number: The tool's version number (User interface or the Command Line Interface).

General Summary

• Total Files: The file count found in the input path of the migration.

• Conversion Speed: The lines transformed per second.

• Total Lines of code: The count of lines of code processed by the tool.

• Assessment speed: The time the tool takes to count, transform and calculate the conversion rates of the source code.

SQL Conversion Summary

• Lines of Code: The count of lines of code just for SQL files.

• Unrecognized Lines of Code: The lines of code that the tool couldn't recognize. Those lines are mostly represented by parsing errors and are not part of the identified objects.

• Code/LOC Conversion Rate: The percentage of code that was successfully converted from the input SQL files. This is an estimation of the conversion rate based on the characters or lines of code depending on the chosen conversion rate mode. This conversion rate is negatively affected by parsing errors, objects that weren’t recognized, code that is unsupported in snowflake, and errors that occurred during the conversion.

See also our glossary that provides a more detailed explanation of the concepts mentioned above.

Objects Conversion Summary

• Identified Objects: The number of objects that were recognized by SnowConvert.

• Fully Converted Objects: The number of objects that were transformed with no issues.

• Unrecognized Elements: The number of statements that couldn't be recognized by the tool.

• Objects Conversion Rate: The percentage of identified objects that were fully converted. This conversion rate doesn't consider the unrecognized elements in its calculation.

See also our glossary that provides a more detailed explanation of the concepts mentioned above.

Script Conversion Summary

This summary is only enabled for Teradata.

• Identified Objects: The number of objects inside Script files that were recognized by SnowConvert.

• Unrecognized Elements: The number of statements inside Script files that couldn't be recognized by the tool.

• LOC Conversion Rate: The percentage of code that was successfully converted from the input Script files. This is an estimation of the conversion rate based on the lines of code. This conversion rate is negatively affected by parsing errors, objects that weren’t recognized, code that is unsupported in snowflake and errors that occurred during the conversion.

See also our glossary that provides a more detailed explanation of the concepts mentioned above.

Action Items Summary

• Total Conversion Errors: The number of exceptions that happened during the transformation. This number is based on the MSCEWI1013 count.

• Total Parsing Errors: The count of parsing errors in all the files inside the input path.

• Total Warnings: The number of issues with Low severity identified by the tool during the transformation.

• Total Files Not Generated: The number of files not generated.

See also our glossary that provides a more detailed explanation of the concepts mentioned above.

File and Object Level Breakdown

This section will provide more detailed information about the migrated files and the objects found inside each file type.

SQL Files

• Total Files: The SQL file count found in the input path of the migration.

• Total Lines of code: The count of lines of code inside SQL files processed by the tool.

• Total Object Quantity: The number of objects that the tool was able to recognize inside SQL files.

• Parsing Errors: The count of parsing errors in the SQL files inside the input path.

• Code Conversion Rate: The percentage of code that was successfully converted from the input SQL files. This is an estimation of the conversion rate based on the characters or lines of code depending on the chosen conversion rate mode. This conversion rate is negatively affected by parsing errors, objects that weren’t recognized, code that is unsupported in snowflake, and errors that occurred during the conversion.

SQL/DML/DDL Identified Objects

• Object: Contains the top-level object type name.

• Object Conversion Rate: The percentage of SQL objects of the specific type that were fully converted. This conversion rate doesn't consider the unrecognized elements in its calculation.

• Code/LOC Conversion Rate: The percentage of the object type that was successfully converted from the input SQL files. This is an estimation of the conversion rate based on the characters or lines of code depending on the chosen conversion rate mode. This conversion rate is negatively affected by parsing errors, objects that weren’t recognized, code that is unsupported in snowflake and errors that occurred during the conversion.

• Total Object Quantity: The number of identified top-level objects of the specific type inside SQL files.

• Total LOC: The overall lines of code count of the top-level objects of the specific type inside SQL files.

• Parsing Errors: The number of parsing errors inside the top-level object of the specific type.

• Conversion Errors: The number of MSCEWI1013 occurrences inside top-level objects of the specific type.

A top-level object is considered by the tool as a DDL or DML statement that encapsulates base functionality, such as Tables, Views, Procedures, etc. They vary from language to language. Please refer to the translation reference of each tool to know more about the supported objects.

If a hyphen (‘-’) is listed in the table above, it means no objects of that kind were found in the input folder.

If an object has parsing errors doesn't mean that it was not identified at all.

Script Files

This section is only enabled for Teradata.

• File: The type of file.

• Total Files: The Script files count found in the input path of the migration.

• Total Lines of code: The count of lines of code inside Script files processed by the tool.

• Parsing Errors: The count of parsing errors in the Script files inside the input path.

• Conversion Errors: The number of MSCEWI1013 occurrences identified in all the script files during transformation.

• Files Generated: The percentage of files that were generated. This conversion rate is negatively affected if there are files not generated in the output folder.

• LOC: The percentage of code that was successfully converted from the input Script files. This is an estimation of the conversion rate based on the lines of code. This conversion rate is negatively affected by parsing errors, objects that weren’t recognized, code that is unsupported in snowflake and errors that occurred during the conversion.

In Teradata, script files are considered files with BTEQ, FLOAD, MLOAD, TPUMP or

TPT extension.

The table above shows a more detailed summary of each of the Script files identified for the specific source language.

• Object: Contains the script file extension name.

• Object Conversion Rate: The percentage of files of the specific extension that were generated.

• LOC Conversion Rate: The overall Lines of Code conversion percentage of all the files of a specific extension. This conversion rate is negatively affected by parsing errors, objects that weren’t recognized, code that is unsupported in snowflake and errors that occurred during the conversion.

• Total Object Quantity: The number of files of a specific extension.

• Total LOC: The overall lines of code count of the files with the same extension.

• Parsing Errors: The number of parsing errors found in files of the same extension.

• Conversion Errors: The number of MSCEWI1013 occurrences inside files of the same extension.

Issues Breakdown

This section shows at most the top 10 issue items identified during the transformation. You can click them, and you will be redirected to the documentation where you can find more information, code examples, and recommendations for each issue.

Issues with LOW severity are not included in the table.

Action items: Pieces of code that might require manual work or inspection after running SnowConvert.

Number of issues: The total number of issues of each severity. There can be issues with the same code in each severity.

Number of unique issues: The total number of issues of each severity. It only counts an issue of a specific code once.

Top Issues Items Distribution

Along with the information reported in the previous section, this card shows a chart with the top action items percentage and the “other action items” percentage which represents the rest of the manual work summarized.

View Complete Reports

This button will redirect the user to the directory where all the reports are generated, look for the Top level objects report to check the object inventory that the tool was able to recognize and transform.