Issues and Troubleshooting
In this section, you will find information about Errors, Warnings, and Issues on the SnowConvert.
This is a deprecated version of the SnowConvert documentation, please visit the official site HERE.
Before we get too far down the troubleshooting road, recall that we highly recommend that you go through our training labs in order to get the most out of SnowConvert.
Conversions of any large quantity of code will likely have a few errors and warnings. When using any of our tools, you can count on us to be your partner in resolving any errors you may encounter.
Below is a list of specific conversion issues for TransactSQL that you may see when you perform a conversion with SnowConvert along with a severity level for each. Some suggested solution paths based on the severity level will follow the list of codes.
Take a minute to read through the list and the troubleshooting tips to help diagnose some of the error codes you have encountered. If you have a question that cannot be answered here, please reach out! You can drop us an email at snowconvert-support@snowflake.com. This is a living list, so it will grow and change as SnowConvert evolves. Updates to issue and error handling will appear on this page, and will also appear in the release notes.
Issues Code
Here is the list of issue codes that exist in SnowConvert for SQL Server platform. A detailed description of each issue code with its respective severity level can be seen in the following table.
| Code | Description | Severity |
|---|---|---|
Transformation for USE database is disabled by default | Low | |
Constraint in default expression not supported | Low | |
Encrypted with not supported in Snowflake | Low | |
Collation for values KS, WS not supported | Low | |
Collation Albanian_bin not supported | Low | |
Selection of variable may have runtime errors | Low | |
Performance warning - recursion for CTE not checked. Might require recursive keyword | Low | |
Failed to transform Unicode literal | High | |
The default value is not supported by Snowflake. | Low | |
Default value added. | Low | |
Column sorting removed | Low | |
Computed column transformed | Low | |
The computed expression could not be upgraded | Low | |
With partitions clause in truncate statement is not supported | Medium | |
Database console command is not supported | Medium | |
ODBC Scalar Function is not supported | Medium | |
Column masking not supported | Low | |
Object_Id replace with select statement | Low | |
CROSS APPLY not supported | Medium | |
Common Table Expression not supported | Low | |
If Statement With Object ID Removed | Low | |
PUT statement not supported on UI | Low | |
Bulk option not supported | Low | |
Incomplete transformation for Bulk Insert | Low | |
ERROR_SEVERITY function transformed | Low | |
Low | ||
Low | ||
Labels inside user-defined function were removed | Low | |
Information for the column was not found. STRING used to match CAST operation | Medium | |
Warning while OUTER JOIN equivalence is checked | Low | |
Information for the expression was not found. CAST to STRING used | Medium | |
Bulk Insert Partially Translated | High | |
PUT not supported inside dynamic SQL | High | |
RETURNS clause incomplete due to missing symbols | High | |
Declaring a Cursor Variable that it is never initialized is not supported. | Medium | |
Snowflake Scripting only supports Local Cursors. | Medium | |
Snowflake Scripting Cursors are non-scrollable. | Medium | |
Snowflake Scripting cursor rows are not modifiable. | Medium | |
Multiple SET Statements for the same cursor found. | Medium | |
Value overwritten, check function equivalence. | Medium | |
XML data type methods are not supported in Snowflake. | Medium | |
OPENXML clause is not supported in Snowflake. | Medium | |
WITH XMLNAMESPACES is not supported in Snowflake. | Medium | |
FOR XML clause is not supported in Snowflake. | Medium | |
Labeled Statement is not supported in Snowflake Scripting. | Low | |
System table is not supported in Snowflake. | Medium | |
RAISERROR Error Message may differ because of the SQL Server string format. | Medium | |
Alter Table translation planned to be delivered in the future. | Medium | |
Multiple Line If Body translation planned to be delivered in the future. | Medium | |
Valid Default Constraint moved to a new Alter Table Statement. | Low | |
Some table elements may have been removed from Add clause. | Medium | |
Some functional table elements may have been reordered to a new Alter Table statement. | Medium | |
Multiple selects in if body were partially transformed. | High | |
Explicit cast to DATE added to return value. | Low | |
Default constraint was commented out and may have been added to a table definition. | Medium | |
A MASKING POLICY was created as a substitute for MASKED WITH. | Low | |
Masking role must be defined previously by the user. | Low | |
One or more of the table element parts are not supported in snowflake. | Medium | |
Column data type is not supported in Snowflake. | Medium | |
Datetime interval not supported by Snowflake. | Medium | |
[DEPRECATED] | ||
Warning Precision in Convert Date and Time Zone. | Low | |
Time zone not supported in Snowflake. | Critical | |
XP_LOGININFO mapped to custom UDF. | Low | |
FORMATMESSAGE function was converted to UDF. | Low | |
Routine option not supported in Snowflake. | Low | |
Invalid parameters in OPENXML table-valued function. | Critical | |
Timestamp format was not found. | Low | |
CURRENT_DATABASE function has different behavior in certain cases. | Low | |
CURRENT_TIMESTAMP in the At Time Zone statement may have a different behavior in certain cases. | Low | |
CURRENT_USER function does not support a user ID as a parameter. | Medium | |
The RETURN statement will be ignored due to the previous RETURN statement | Low | |
Error message could be different in Snowflake | Low |
Issues Severity
In this section, you can find an explanation of the severities.
Low
Warnings for source code that there was no direct conversion to Snowflake. The code has been converted to a functionally equivalent output but should still be reviewed.
Medium
Errors that produce a functional or runtime difference. The user may have to invest a low amount of manual effort to complete the conversion.
High
Errors that produce a functional or runtime difference. The user may have to invest a high amount of manual effort to complete the conversion.
Critical
Parsing errors or errors that cause significant conversion exceptions in SnowConvert. If the source code is correct, a significant intervention will be required.
Need more support?
As has been mentioned previously in this article, please reach out to us if you need more support. Snowflake wants to be your partner in the conversion process, so let us know how we can help. You can email us at snowconvert-support@snowflake.com. If you have a contract for support with Snowflake, reach out to your sales engineer and they can direct your support needs.
Last updated