Conversion Issues
In this section, you will be able to find all the SnowConvert common issues with their respective description and possible solution.
Last updated
In this section, you will be able to find all the SnowConvert common issues with their respective description and possible solution.
Last updated
This is a deprecated version of the SnowConvert documentation, please visit the official site .
Here is the list of generic issue codes that exist in SnowConvert across all platforms. A detailed description of each issue code with its respective severity level can be seen in the following table.
Error parsing the source code
Critical
Removed next statement, not applicable in SnowFlake
Low
Error executing a SQL conversion rule
Critical
Error executing a script conversion rule
Critical
File not generated log
Critical
Error writing the top-level objects file
Critical
Error writing the output file
Critical
Expression at time zone changed
Low
Error converting a top-level object
Critical
No rule for procedure statement
Critical
Unexpected end of the statement
High
Unexpected end of the statement check line
High
An Exception is thrown during conversion
Critical
Procedure body not generated
Critical
The input pivot/unpivot statement form is not supported
Medium
Error writing details file
Critical
Error writing summary file
Critical
Error writing issues file
Critical
Error writing the assessment report file
Critical
Custom UDF Inserted
Low
Syntax not supported
Medium
Parameter missing dependency
Medium
Loop performance review
Low
Check constraint commented
Low
Binding time variables might require a change
Low
Qualified variables may require a cast
Low
Variable with invalid query
Medium
Type not supported
Medium
No rule found for SQL node
Critical
No rule was found for BTEQ node
Critical
Function with Pending Equivalence Review
Medium
Cast type not supported
Medium
Semantic information not found
Low
Format removed
Low
CHECK statement not supported
Low
Data type converted to another data type
Low
Translation planned for the future
Medium
Dynamic SQL statement may be unrecognized
Low
Semantic information could not be loaded
Low
Statement Not Supported
Low
Crash parsing the source code file
Critical
Non-relevant syntax
Low
Translation for expression not supported
Medium
Type changed to Date
Low
Column name is a reserved keyword in Snowflake
Medium
Verification of functional equivalence for function is pending
Low
The statement was converted but its functionality is not implemented yet
Medium
Sequence warning.
Low
Not recognized function.
Low
Missing dependent object
Low
Unrecognized or unsupported parameter data type.
Medium
Unusable object.
Medium
Object may not work.
Low
Unsupported outer join subquery
Low
Data Type Not Recognized
Low
Custom Types Not Supported
Low
Create Type Variant Not Supported
High
Functionality is not currently supported by Snowflake Scripting
Medium
Non-Ansi Outer Join is not supported in OR predicate
Medium
Non-Ansi Outer Join to multiple tables is not supported in Snowflake
High
Column does not come from a Non-Ansi Outer Join Expression
Low
Custom type usage changed to variant
Low
Added statements because object used a custom type
Low
Referenced custom type in query not found
High
Columns from expression not found
High
Number type column may not behave similarly in Snowflake
Low
UDF was transformed to Snowflake procedure, calling procedures inside a query is not supported
High
User defined function was transformed to a Snowflake procedure
Low
User defined function inner logic was transformed to a single Common Table Expression
Low
User defined function body not generated
Critical
User defined function structured block was transformed to a single SQL Query
Low
Window frame unit was changed to Rows
Low
Pending Functional Equivalence Review
Medium
Suffixes in numeric literals were removed
Low
Current Of Clause is Not Supported
High
Constants are not supported by Snowflake Scripting. It was transformed to a variable.
Low
Cycle Found between CTE calls
Low
Output parameters are not supported by Snowflake Scripting
Medium
Parameter names were removed from call
Low
Default value is not allowed on binary columns
Low
Snowflake Scripting procedure cannot return more than one result set
Medium
Auto-Generated code in order to support the output parameters functionality in Snowflake Sripting
Low
Output parameters are not supported by Snowflake Scripting but their functionality is being emulated
Low
XMLTABLE is not supported.
High
Helper file generated for object
Low
Replaced invalid characters for new identifier
Low
Arguments do not match the called procedure parameters count, default parameters are not supported yet
Low
Default value removed
Low
Default value added
Low
Create Index Not Supported
High
Materialized View was converted to regular View
Low
On Commit not supported
Medium
Label declaration not supported
Low
Object not renamed
Low
TIME ZONE not supported for time data type
Medium
Constraint in default expression is not supported.
Low
Precision in milliseconds reduced to three digits.
Low
Create table as subquery with no data is not supported in Snowflake
Low
Multiple result sets are returned in temporary tables
Low
Transaction label names are not supported in Snowflake
Low
The statement option is removed and handled by conversion.
Low
Snowflake does not have a PURGE clause inside the DROP TABLE statement
Low
Have an issue related to a specific source platform? Check out the individual pages for each source SnowConvert platform:
In this section, you can find an explanation of the severities.
Informative notes for the user about successful conversion scenarios. No further action is needed. Some examples include:
Code converted to a functionally equivalent output but that was emulated through a conversion workaround (primarily due to non-existing functionality in Snowflake)
Code that is removed from the output because is no longer required (primarily due to architectural reasons)
Warnings for the user about successful conversion scenarios that might be helpful to review. Some examples include:
Code converted to a functionally equivalent output but
might still present minor differences in specific situations.
might have performance issues in specific cases.
some code improvements were not applied due to missing dependencies (tables, views definitions) in the input source code.
Errors that produce a functional or runtime difference. The user may have to invest a low amount of manual effort to complete the conversion.
Errors that produce a functional or runtime difference. The user may have to invest a high amount of manual effort to complete the conversion.
Errors that cause exceptions in SnowConvert. If the input source code is correct, a significant manual intervention will usually be required to complete the conversion. Examples are parsing and conversion errors.
​​
Reach out! Whether you need additional support working through migration or if you need an additional feature, let us know. We are your partner in the conversion process. You can email us at . If you have a contract for support, reach out to your sales engineer and they can direct your support needs.