Transact-SQL Conversion Settings
Last updated
Last updated
Transform use database: Flag to indicate whether or not the Transact SQL USE statement should be translated.
Comment objects with missing dependencies: Flag to indicate if the user wants to comment on nodes that have missing dependencies.
Disable EWI comments generation (errors, warnings and issues): Flag to indicate whether EWIs comments (Errors, Warnings, and Issues) will not be generated on the converted code. The default is false
Set encoding of the input files: The encoding code page number is used for parsing the source files. We only accept encodings supported by .NET Core. Here are the ones supported at the moment:
Code Page
Name
Display Name
1200
utf-16
Unicode
1201D
unicodeFFFE
Unicode (Big endian)
12000
utf-32
Unicode (UTF-32)
12001
utf-32BE
Unicode (UTF-32 Big endian)
20127
us-ascii
US-ASCII
28591
iso-8859-1
Western European (ISO)
65000
utf-7
Unicode (UTF-7). Not available in .NET 5
65001
utf-8
Unicode (UTF-8). Default encoding
To review the Settings that apply to all supported languages, go to the following article.
Schema: The string value specifies the custom schema name to apply. If not specified, the original database name will be used. Example: DB1.myCustomSchema.Table1.
Database: The string value specifies the custom database name to apply. Example: MyCustomDB.PUBLIC.Table1.
Default: None of the above settings will be used in the objects names.
Prepare my code: Flag to indicate whether or not to preprocess or arrange the source code before its transformation. By default, it's set to FALSE.
Pretty print: Applies indentation to the original code and get it well organized.
Maintain the input folder structure: Generates extra reports after the arrangement.
Multiple: Applies arrangement to multiple databases represented as multiple folders, and keeps their original structure.
You can read the entire arrange documentation in the arrange documentation page
On this page, you can choose whether the successfully converted code percentage is calculated using lines of code or using the total number of characters. Characters conversion rate is the default option. You can read the entire rate documentation in the documentation page.
On this page, you can choose whether stored procedures are migrated to JavaScript embedded in Snow SQL, or to Snowflake Scripting. The default option is Snowflake Scripting.
Reset Settings: The reset settings option appears on every page. If you've made changes, you can reset SnowConvert to its original default settings.
