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.

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 PostgreSQL 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 [e-mail]. 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.

Issues Code

Here is the list of error codes that SnowConvert might generate for PostgreSQL conversions. A description of the severity levels and some troubleshooting suggestions will follow this list of codes.

Code	Description	Severity
MSC-PG0000	User privileges must be handled manually.	Low
MSC-PG0001	Age not supported	Medium
MSC-PG0002	Bpchar converted to varchar	Low
MSC-PG0003	Bytea Converted To Binary	Low
MSC-PG0004	The date output format may vary	Low
MSC-PG0005	Set search path with multiple schemas	Medium
MSC-PG0006	Raise notice translated to user-defined stored procedure.	Low
MSC-PG0007	Constraint index parameter not supported	Low
MSC-PG0008	Inheritance not supported	Low
MSC-PG0009	Exclude constraint not supported	Medium
MSC-PG0010	Precision format is not supported in Snowflake.	Medium
MSC-PG0011	The current to_char date format may have a different behavior in Snowflake.	Low
MSC-PG0012	The current to_char numeric format may fail or have a different behavior in Snowflake.	Medium
MSC-PG0013	Unsupported Raise Exception.	Medium
MSC-PG0014	Raise Exception translated to user-defined stored procedure call and raise stat.	Low
MSC-PG0015	The current Timestamp format may have a different behavior in Snowflake.	Low
MSC-PG0016	The lock level is handled automatically in Snowflake.	Low
MSC-PG0017	Select with Into clause is not compatible with snowflake, it is transformed to a Create Table As.	Low
MSC-PG0018	Select with Into clause is not compatible with snowflake, it is transformed.	Low
MSC-PG0019	The use of Invertal within a to_char function is not compatible with Snowflake.	High
MSC-PG0020	Comment on 'Type' is not supported by Snowflake.	Low
MSC-PG0021	NULL is converted to '' and may have a different behavior in Snowflake.	Low
MSC-PG0022	Materialized view is only supported in the enterprise version of Snowflake.	Low
MSC-PG0023	The argument mode (IN, OUT, INOUT, VARIADIC) are not supported by Snowflake. By default, all the arguments are in IN mode.	Low
MSC-PG0024	Advance sequence and return new value.	Low
MSC-PG0025	Sequence 'TEMPORARY | Temp' is not supported by Snowflake.	Low
MSC-PG0026	The sequence option 'option_name' is not supported by Snowflake.	Low
MSC-PG0027	FOUND could have a different behavior in Snowflake in some scenarios.	Low
MSC-PG0028	TRUNCATE RESTRICT BEHAVIOR SHOULD BE USED WHEN NOT HAS REFERENCES	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 functional 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, significant intervention will be required.