Complex Pattern Issues
This page contains the Issues related to the complex patterns detected inside the code with their respective description and recommended actions.
This is a deprecated version of the SnowConvert documentation, please visit the official site HERE.
The complex pattern issues related to Stored Procedures are generated only when the Target Language for Stored Procedures/Macros is set to Snowflake Scripting.
| Code | Description | Severity |
|---|---|---|
The following subquery matches at least one of the patterns considered invalid and may produce compilation errors | Medium | |
The following table was GLOBAL TEMPORARY on the source code, which is not supported on the target language. | Low | |
The statement below has usages of cursor for loop | Low | |
The statement below has usages of dynamic SQL | High | |
The statement below has usages of cursor fetch bulk operations | Low | |
Fetch inside a loop is considered a complex pattern, this could degrade Snowflake performance | Low | |
Case insensitive columns can decrease performance of queries | Low | |
Nested function/procedure declarations are considered a complex pattern and not supported in snowflake. | Low | |
The following transaction may contain nested transactions and this is considered a complex pattern not supported in Snowflake. | Low | |
The statement below has usages of nested cursors. | Low | |
Nested cursor inside query is not supported in Snowflake. | Medium |
Issues Severity
In this section, you could 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?
Reach out! Whether you need additional support working through migration or if you need an additional feature, let us know. Snowflake is here to be your partner in the conversion process. 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