SnowConvert: Glossary¶

​Glossary¶

This section explains common concepts found across multiple SnowConvert report documents.

• Total Conversion Issues: The number of critical errors that occurred during conversion, such as file I/O problems or memory management issues.

• Total Parsing Errors: The number of errors found when analyzing the code. These occur when the parser encounters unexpected code or syntax that doesn’t match SQL grammar rules. High numbers suggest code review is needed.

• Total Warnings: The number of cases where the converted code is mostly equivalent but may need review. These are low-severity notifications for potential differences in functionality.

• Total Lines of Code (LOC): The number of actual code lines, excluding comments and blank lines.

• Identified Code Units: The number of standalone database objects like TABLES, VIEWS, and PROCEDURES. These may contain smaller definitions within them.

• Unrecognized Elements: Code components that SC couldn’t process due to parsing errors.

• Lines of Code in Unrecognized Elements: The total number of code lines that SC failed to process.

• Fully Converted Code Units: The number of complete database objects converted without errors and ready for deployment.

• **Code Conversion Rate (SQL): this metric is calculated using as reference the source code of both recognized and unrecognized elements in the given workload. The conversion rate is the percentage of source code that was successfully converted by SnowConvert into functionally equivalent Snowflake code. Take into consideration that unrecognized elements (because of parsing issues) will affect this metric, as their source code will be counted as not converted. Furthermore, elements that do not have equivalence in Snowflake will also punish the conversion rate, because even though SnowConvert is able to process them (frequently by removing them or commenting them) the translation does not represent a functionally equivalent code. For example, if there is a lot of code of indexes (which do not have an equivalent in Snowflake) the conversion rate can be highly punished because the source code of those unsupported elements might represent a significant part of the overall workload.

• Code Unit Conversion Rate, the percentage between fully converted code units and identified code units.

• Code Unit Conversion Rate: The percentage of fully converted database objects compared to total identified objects.

• Assessment report data: How SC presents analysis results:

  • “0” represents zero value

  • “-” means no code units exist

  • “N/A” indicates unsupported features or non-existent Snowflake equivalents

​Assessment Report (docx)¶

The assessment report provides a comprehensive overview of your code migration project. It includes the estimated code conversion rate and valuable insights to help you understand how close you are to achieving functionally equivalent Snowflake code.

​Issues Report¶

The issues report is a file that lists all problems encountered during the migration process.

​HTML report¶

The HTML report summarizes the transformation results. This guide explains how to interpret the report’s contents.

​Elements Report¶

The Elements report provides a detailed count of Grammar Elements discovered during migration. The report organizes elements by multiple columns to distinguish between similar elements used in different contexts. For example, a SELECT query can appear in different locations such as within a PROCEDURE, a VIEW, or a script file. This report helps you understand the elements in detail and monitor their transformation progress.

​Code Unit (CU)¶

SnowConvert analyzes and divides code into smaller, manageable units called code units for reporting purposes. For more information about code unit definitions, please refer to the documentation “here”.

Code Unit Parent Category (CUPC) ¶

For easier analysis, some sections of this document group code units together to show metrics such as conversion rates and counts. You can still find detailed information for each code unit in the main code units document. To learn more about how code units are grouped, please see the documentation [here].