Ispirer Migration Knowledge Base

User Tools

Site Tools

You are here: Ispirer Migration Knowledge Base » Ispirer Migration Knowledge Base » SQLWays Command Line » Sqlways.ini File Sections Overview » Sqlways.ini File - Section [DDL]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

sqlways:command-line:sqlways-ini:ddl-section [September 04, 2018, 12:39:56 PM] – alexandr.kirpichnysqlways:command-line:sqlways-ini:ddl-section [May 31, 2023, 05:28:08 PM] (current) – external edit 127.0.0.1
Line 1: Line 1:
 \\ \\
-[[http://www.ispirer.com|Ispirer Home Page]] +[[https://www.ispirer.com|Ispirer Website]] 
-[[http://www.ispirer.com/products|Ispirer SQLWays Product Page]] +[[https://www.ispirer.com/products/migration-toolkit|Ispirer Toolkit Overview]] 
-[[http://www.ispirer.com/?click=RequestSQLWays&from=IspirerWIKI|Request SQLWays]]+[[https://www.ispirer.com/download/download-demo|Free Trial]]
 ====== Sqlways.ini File - Section [DDL] ====== ====== Sqlways.ini File - Section [DDL] ======
  
-This article describes sqlways.ini file [DDL] section and the options it contains. +This article describes sqlways.ini file's [DDL] section and the options it contains. 
 ^  Option name  ^ Description  ^  ^  Option name  ^ Description  ^ 
 | **GENERATE_DROP_TABLE** | If Yes is specified, the DROP TABLE statement is generated before each CREATE TABLE statement. The default value is No. Possible values - Yes, No. | | **GENERATE_DROP_TABLE** | If Yes is specified, the DROP TABLE statement is generated before each CREATE TABLE statement. The default value is No. Possible values - Yes, No. |
-| **DROP_TABLE_CASCADE_CONSTRAINTS** | If Yes is specified, the CASCADE CONSTRAINTS option is generated in the DROP TABLE statement. Currently this option is supported by Oracle only. \\ This option is only available if the target database is Oracle and GENERATE_DROP_TABLE is set to Yes. The default value is No. |+| **GENERATE_DROP_VIEWS** | If Yes is specified, the DROP VIEW statement is generated before each CREATE VIEW statement. \\ The default value is No. \\ Possible values - Yes, No. | 
 +| **GENERATE_DROP_PROCEDURES** | If Yes is specified, the DROP PROCEDURE statement is generated before each CREATE PROCEDURE statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_FUNCTIONS** | If Yes is specified, the DROP FUNCTION statement is generated before each CREATE FUNCTION statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_TRIGGERS** | If Yes is specified, the DROP TRIGGER statement is generated before each CREATE TRIGGER statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_PACKAGES** | If Yes is specified, the DROP PACKAGE statement is generated before each CREATE PACKAGE statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_USER_ACCOUNTS** | If Yes is specified, the DROP USER statement is generated before each CREATE USER statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_USER_DEFINED_TYPES** | If Yes is specified, the DROP TYPE statement is generated before each CREATE TYPE statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_SEQUENCES** | If Yes is specified, the DROP SEQUENCE statement is generated before each CREATE SEQUENCE statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_SYNONYMS** | If Yes is specified, the DROP SYNONYM statement is generated before each CREATE SYNONYM statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_MACROS** | If Yes is specified, the DROP MACRO statement is generated before each CREATE MACRO statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_EXCEPTIONS** | If Yes is specified, the DROP EXCEPTION statement is generated before each CREATE EXCEPTION statement. The default value is No. Possible values - Yes, No. | 
 +| **GENERATE_DROP_EVENTS** | If Yes is specified, the DROP EVENT statement is generated before each CREATE EVENT statement. The default value is No. Possible values - Yes, No. | 
 +| **DROP_TABLE_CASCADE_CONSTRAINTS** | If Yes is specified, the CASCADE CONSTRAINTS option is generated in the DROP TABLE statement. Currently this option is supported by Oracle only. \\ This option is available only if the target database is Oracle and GENERATE_DROP_TABLE is set to Yes. The default value is No. |
 | **GENERATE_DROP_INDEX** | If Yes is specified, the DROP INDEX statement is generated before each CREATE INDEX statement. The default value is No. Possible values - Yes, No. \\ This option can be helpful when scripts for indexes are re-executed without recreating the table. | | **GENERATE_DROP_INDEX** | If Yes is specified, the DROP INDEX statement is generated before each CREATE INDEX statement. The default value is No. Possible values - Yes, No. \\ This option can be helpful when scripts for indexes are re-executed without recreating the table. |
-| **OUTSCHEMA** | Output schema name. | +| **OUTSCHEMA** | This option can be used only when "EMPTY_SCHEMA" option is set to "No". In this option user can specify a schema name that will be used in the generated target code, instead of original one. When this option is empty, used original schema names. \\ Empty  by default. | 
-| **EMPTY_SCHEMA** | for /EMPS option. Possible values - Yes, No. |+| **EMPTY_SCHEMA** | This option defines whether the schema names should be used in the generated target script. If it is set to "Yes" - schema names will be removed. If set to "No" - schema names will be left as in the generated target code. \\ Possible values - Yes, No. |
 | **COLUMN_NAME_CASE** | This option specifies the case of column names in SQL statements. Possible values - Upper, Lower. If no value is specified, the case of the column names is not changed and column names are used as they are provided in the source database. | | **COLUMN_NAME_CASE** | This option specifies the case of column names in SQL statements. Possible values - Upper, Lower. If no value is specified, the case of the column names is not changed and column names are used as they are provided in the source database. |
 | **USE_CONSTRAINT_NAMES** | If Yes is specified, constraint names of the source database will be used in generated DDL scripts. Otherwise, constraint names will be skipped. The default value is No. Possible values - Yes, No. | | **USE_CONSTRAINT_NAMES** | If Yes is specified, constraint names of the source database will be used in generated DDL scripts. Otherwise, constraint names will be skipped. The default value is No. Possible values - Yes, No. |
-| **PK_COLS_NOTNULL** | This option is used to set the NOT NULL constraints in the CREATE TABLE statement for columns making up a primary key. The default value is Yes. Possible values - Yes, No. Some databases (Oracle, Sybase, Access e.g.) allow to not specify the NOT NULL constraints for primary key columns explicitly when creating a table, and they change columns to NOT NULL when adding a primary key. Other databases (IBM DB2, Microsoft SQL Server, MySQL e.g.) require primary key columns to be created with NOT NULL constraints before adding a primary key. \\ The default value is Yes (all primary key columns will be created with NOT NULL constraints). Possible values - Yes, No. |+| **PK_COLS_NOTNULL** | This option is used to set the NOT NULL constraints in the CREATE TABLE statement for columns making up a primary key. The default value is Yes. Possible values - Yes, No. Some databases (Oracle, Sybase, Access e.g.) allow not to specify the NOT NULL constraints for primary key columns explicitly when creating a table, and they change columns to NOT NULL when adding a primary key. Other databases (IBM DB2, Microsoft SQL Server, MySQL e.g.) require primary key columns to be created with NOT NULL constraints before adding a primary key. \\ The default value is Yes (all primary key columns will be created with NOT NULL constraints). Possible values - Yes, No. |
 | **CONVERT_IDENTITY_COLUMNS** | If Yes is specified, SQLWays converts identity properties of columns. Otherwise, SQLWays does not extract the identity properties. The default value is Yes. Possible values - Yes, No. | | **CONVERT_IDENTITY_COLUMNS** | If Yes is specified, SQLWays converts identity properties of columns. Otherwise, SQLWays does not extract the identity properties. The default value is Yes. Possible values - Yes, No. |
 | **REMOVE_NOTNULL_EXCEPT_PK** | If Yes is specified, the NOT NULL constraints for all columns except primary key columns in the target database are removed to avoid their conversion between databases by SQLWays. The default value is No. Possible values - Yes, No. \\ Identity columns are commonly used in conjunction with primary key constraints to serve as a unique row identifier for a table. | | **REMOVE_NOTNULL_EXCEPT_PK** | If Yes is specified, the NOT NULL constraints for all columns except primary key columns in the target database are removed to avoid their conversion between databases by SQLWays. The default value is No. Possible values - Yes, No. \\ Identity columns are commonly used in conjunction with primary key constraints to serve as a unique row identifier for a table. |
Line 20: Line 32:
 | **STATEMENT_DELIMITER** | Statement termination character. | | **STATEMENT_DELIMITER** | Statement termination character. |
 | **STATISTICS_STATEMENTS** | This option specifies whether statements to calculate statistics on tables in DDL scripts for table indexes should be generated.The default value is Yes. Possible values - Yes, No. Currently SQLWays generates statistics statements for IBM DB2 only. | | **STATISTICS_STATEMENTS** | This option specifies whether statements to calculate statistics on tables in DDL scripts for table indexes should be generated.The default value is Yes. Possible values - Yes, No. Currently SQLWays generates statistics statements for IBM DB2 only. |
-| **PK_UNIQUE_INDEXES** | This option specifies whether indexes on primary keys and unique constraints should be generated. The default value is No. This means no index scripts are generated for primary keys and unique constraints. In this case the database creates unique indexes for primary keys and unique constraints implicitly. \\ If the unique indexes with the same definition as required for primary keys and unique constraints were created before creating primary keys and unique constraints, the database uses these indexes for primary keys and unique constraints. \\ When PK_UNIQUE_INDEXES=ALWAYS is specified, index scripts for primary and unique constraints are always created. This allows to create indexes before creating primary keys and unique constraints. |+| **PK_UNIQUE_INDEXES** | This option specifies whether indexes on primary keys and unique constraints should be converted. The default value is No. This means that indexes and unique constraints will not be converted for primary key columns, if they exist in the source database. It is developed for cases when the database creates unique indexes for primary keys and unique constraints implicitly by itself. \\ If the unique indexes with the same definition as required for primary keys and unique constraints were created before creating primary keys and unique constraints, the database uses these indexes for primary keys and unique constraints. \\ When PK_UNIQUE_INDEXES=ALWAYS is specified, index scripts for primary and unique constraints are always created. This allows to create indexes before creating primary keys and unique constraints. |
 | **REPLACE_NOT_ALLOWED_CHARS** | This option specifies a character or a string that replaces not allowed characters in identifiers in the target database. \\ The source database may allow users to use characters in identifiers (table and column names etc.) which are not allowed in the target database. \\ For example, users can use @ in identifiers in Microsoft SQL Server, but this character is not allowed in identifiers in Oracle. \\ If no value is specified in this option and "remove_not_allowed_chars=no", then all not allowed characters are left in identifiers for the target database. | | **REPLACE_NOT_ALLOWED_CHARS** | This option specifies a character or a string that replaces not allowed characters in identifiers in the target database. \\ The source database may allow users to use characters in identifiers (table and column names etc.) which are not allowed in the target database. \\ For example, users can use @ in identifiers in Microsoft SQL Server, but this character is not allowed in identifiers in Oracle. \\ If no value is specified in this option and "remove_not_allowed_chars=no", then all not allowed characters are left in identifiers for the target database. |
-| **REMOVE_NOT_ALLOWED_CHARS** | This option is similar to the replace_not_allowed_chars option, but it allows you to remove not allowed characters in identifiers in the target database. \\ When Yes is specified, all not allowed characters are removed in identifiers in the target database. \\ The default value is Yes. Possible values - Yes, No. |+| **REMOVE_NOT_ALLOWED_CHARS** | This option is similar to the replace_not_allowed_chars option, but it allows you to remove not allowed characters in identifiers in the target database. \\ When Yes is specified, all not allowed characters are removed from identifiers in the target database. \\ The default value is Yes. Possible values - Yes, No. |
 | **REPLACE_NOT_ALLOWED_CHARS_FPOS** | This option specifies a character or a string that replaces not allowed characters in the first position of identifiers in the target database. \\ Characters that are allowed in the first position of identifiers in the source database may not be allowed in the target database. \\ For example, Microsoft SQL Server identifiers can begin with _ (underscore) while Oracle identifiers cannot. \\ If no value is specified in this option and "remove_not_allowed_chars_fpos=no", then all not allowed characters are left in the first position of identifiers for the target database. | | **REPLACE_NOT_ALLOWED_CHARS_FPOS** | This option specifies a character or a string that replaces not allowed characters in the first position of identifiers in the target database. \\ Characters that are allowed in the first position of identifiers in the source database may not be allowed in the target database. \\ For example, Microsoft SQL Server identifiers can begin with _ (underscore) while Oracle identifiers cannot. \\ If no value is specified in this option and "remove_not_allowed_chars_fpos=no", then all not allowed characters are left in the first position of identifiers for the target database. |
 | **REMOVE_NOT_ALLOWED_CHARS_FPOS** | This option is similar to the replace_not_allowed_chars_fpos option, but it allows users to remove not allowed characters in the first position of identifiers in the target database. \\ When Yes is specified, all not allowed characters are removed in the first position of identifiers in the target database. \\ The default value is Yes. Possible values - Yes, No. | | **REMOVE_NOT_ALLOWED_CHARS_FPOS** | This option is similar to the replace_not_allowed_chars_fpos option, but it allows users to remove not allowed characters in the first position of identifiers in the target database. \\ When Yes is specified, all not allowed characters are removed in the first position of identifiers in the target database. \\ The default value is Yes. Possible values - Yes, No. |
-| **TRIM_NAMES_EXCEEDING_MAX_LEN** | Databases may have different identifier length limits. For example, the maximum identifier length in SQL Server is 128 characters while in Oracle - 30. An error occurs when a table with a name exceeding 30 characters is migrated from SQL Server to Oracle. \\ If Yes is specified, SQLWays trims off identifiers exceeding the maximum length for the target database. If during the trimming SQLWays gets identical identifiers, it replaces the last characters of these identifiers (except the first identifier) with numbers in the ascending order beginning with "2". \\ For example, if after trimming SQLWays gets two identical identifiers like "home_phone_numbers" etc., they are further converted to: "home_phone_numbers" and "home_phone_number2". \\ If No is specified, SQLWays does not trim identifiers exceeding the maximum length for the target database. \\ The default value is Yes. Possible values - Yes, No. | +| **TRIM_NAMES_EXCEEDING_MAX_LEN** | Databases may have different identifier length limits. For example, the maximum identifier length in SQL Server is 128 characters while in Oracle it is 30. An error may occur when a table with a name exceeding 30 characters is migrated from SQL Server to Oracle. \\ If Yes is specified, SQLWays trims off identifiers exceeding the maximum length for the target database. If during the trimming SQLWays gets identical identifiers, it replaces the last characters of these identifiers (except the first identifier) with numbers in the ascending order beginning with "2". \\ For example, if after trimming SQLWays gets two identical identifiers like "home_phone_numbers" etc., they are further converted to: "home_phone_numbers" and "home_phone_number2". \\ If No is specified, SQLWays does not trim identifiers exceeding the maximum length for the target database. \\ The default value is Yes. Possible values - Yes, No. | 
-| **TRIM_RULE_ALPHANUM_ONLY** | This option is used in conjunction with the "trim_names_exceeding_max_len=yes" option. \\ If Yes is specified and an identifier exceeds the maximum length for the target database, SQLWays first of all deletes all non-alphanumeric characters and then, if the identifier's length is still more than the maximum length, it is trimmed. If No is specified, SQLWays immediately trims the identifiers without deleting the non-alphanumeric characters. \\ For example, if Yes is specified, SQL Server identifier like "regional_customer_account_number#" (33 characters) is converted to "regionalcustomeraccountnumber" (29 characters). \\ The default value is Yes. Possible values - Yes, No. | +| **TRIM_RULE_ALPHANUM_ONLY** | This option is used in conjunction with the "trim_names_exceeding_max_len=yes" option. \\ If Yes is specified and an identifier exceeds the maximum length for the target database, SQLWays firstly deletes all non-alphanumeric characters and then, if the identifier's length is still more than the maximum length, trims it. If No is specified, SQLWays immediately trims the identifiers without deleting the non-alphanumeric characters. \\ For example, if Yes is specified, SQL Server identifier like "regional_customer_account_number#" (33 characters) is converted to "regionalcustomeraccountnumber" (29 characters). \\ The default value is Yes. Possible values - Yes, No. | 
-| **REPLACE_RESERVED_WORDS** | This option is used to change identifiers of the source database which served as reserved words in the target database. The option specifies a template for reserved words replacement. \\ For example, if %RWORD%_ is specified, underscore character is added to the right of all reserved words. \\ The default value of the template is %RWORD% which means that the reserved words are not changed and are delimited in SQL statements for the target database. The delimeter depends on a database. | +| **TRIM_RULE_ALPHANUM_STOP_WHEN_LIMIT_REACHED** | This option is used in conjunction with the "TRIM_RULE_ALPHANUM_ONLY=Yes" option. \\ If Yes is specified and an identifier exceeds the maximum length for the target database, SQLWays will delete all non-alphanumeric characters until the identifier's length is equal to the maximum length. If No is specified, SQLWays immediately trims all the non-alphanumeric characters. \\ The default value is No. Possible values - Yes, No. | 
-| **CONVERT_DATABASE_TO_SCHEMA** | This option is used to convert fully qualified names with the database specification. \\ It is required to set this option to Yes to get it work. | +| **TRIM_RULE_CONSONANTS_ONLY** | This option is used in conjunction with the "trim_names_exceeding_max_len=yes" option. \\ If Yes is specified and an identifier exceeds the maximum length for the target database, SQLWays firstly deletes all consonant characters and then, if the identifier's length is still more than the maximum length, trims it. If No is specified, SQLWays immediately trims the identifiers without deleting the consonants characters. \\ The default value is No. Possible values - Yes, No. | 
-| **CONVERT_PACKAGE_TO_SCHEMA** | This option is used to convert the Package name as the schema from an Oracle database. Currently this feature works for MSSQL as a target database only. \\ It is required to set this option to Yes to get it work. | +| **TRIM_RULE_CONSONANTS_STOP_WHEN_LIMIT_REACHED** | This option is used in conjunction with the "TRIM_RULE_CONSONANTS_ONLY=Yes" option. \\ If Yes is specified and an identifier exceeds the maximum length for the target database, SQLWays deletes consonant characters until the identifier's length is equal to the maximum length. If No is specified, SQLWays immediately trims all the consonant characters. \\ The default value is No. Possible values - Yes, No. | 
-| **BUILTIN_FUNCTIONS_NULLIF_CHECK** | This option is used to generate NULLIF check when converting **LTRIM**, **RTRIM**, **SUBSTRING**, **RIGHT**, **REPLICATE** functions and COALESCE(@some_value,'') for the second parameter of the **CHARINDEX** function from Sybase ASE to Microsoft SQL Server. \\ This option is required for compatibility of these functions when empty strings, NULL values or zero lengths are processed. \\ It is required to set this option to Yes to get it work. |+| **TRIM_RULE_LEFTTRIM** | This option is used in conjunction with the "trim_names_exceeding_max_len=yes" option. \\ If Yes is specified and an identifier exceeds the maximum length for the target database, SQLWays trims characters from the left side.\\ The default value is No. Possible values - Yes, No. | 
 +| **REPLACE_RESERVED_WORDS** | This option is used to change identifiers of the source database which serve as reserved words in the target database. The option specifies a template for reserved words replacement. \\ For example, if %RWORD%_ is specified, underscore character is added to the right of all reserved words. \\ The default value of the template is %RWORD% which means that the reserved words are not changed and are delimited in SQL statements for the target database. The delimiter depends on the database. | 
 +| **CONVERT_DATABASE_TO_SCHEMA** | This option is used to convert fully qualified names with the database specification. \\ Please set this option to Yes to get it work. | 
 +| **CONVERT_PACKAGE_TO_SCHEMA** | This option is used to convert the Package name as the schema from an Oracle database. Currently this feature works for MSSQL as a target database only. \\ Please set this option to Yes to get it work. | 
 +| **SCHEMA_TO_OBJ_NAME** | This option is used to convert the schema name as the prefix to the object name. \\ Possible values - "Yes", "No" or Empty. Default value - "No" or Empty. | 
 +| **BUILTIN_FUNCTIONS_NULLIF_CHECK** | This option is used to generate NULLIF check when converting **LTRIM**, **RTRIM**, **SUBSTRING**, **RIGHT**, **REPLICATE** functions and COALESCE(@some_value,'') for the second parameter of the **CHARINDEX** function from Sybase ASE to Microsoft SQL Server. \\ This option is required for compatibility of these functions when empty strings, NULL values or zero lengths are processed. \\ Please set this option to Yes to get it work. |
 | **FULLY_QUALIFY_IDENTIFIERS** | This option is used to generate schema for each referenced object without schema inside a View, Stored Procedure or Function. \\ This option works only if the **EMPTY_SCHEMA** option is set to No. \\ The default value is No. Possible values - Yes, No.| | **FULLY_QUALIFY_IDENTIFIERS** | This option is used to generate schema for each referenced object without schema inside a View, Stored Procedure or Function. \\ This option works only if the **EMPTY_SCHEMA** option is set to No. \\ The default value is No. Possible values - Yes, No.|
-| **CONVERT_ROUTINE_TO_SP_RESULTSET** | If it's Yes, then all the functions and procedures that return values must be converted to stored procedures that return resultset via the SELECT statement.  \\ The default value is No or Empty. Possible values - Yes, No.| +| **CONVERT_ROUTINE_TO_SP_RESULTSET** | If it is set to Yes, all the functions and procedures that return values must be converted to stored procedures that return resultset via the SELECT statement.  \\ The default value is No or Empty. Possible values - Yes, No.| 
-| **OUT_REFCUR_FIRST_POSITION** | This option works together with CONVERT_ROUTINE_TO_SP_RESULTSET and puts OUT parameter to the first position in the parameter list. Also please note, that this option will work only for Oracle version 11 and lower. For Oracle version 12 and higher OUT parameter will not be generated, and will be used PIPELINE functionality. \\ Possible values - "Yes", "No" or Empty. \\ Default values - "No" or Empty. |+| **OUT_REFCUR_FIRST_POSITION** | This option works together with CONVERT_ROUTINE_TO_SP_RESULTSET and puts OUT parameter to the first position in the parameter list. Also please note, that this option will work only for Oracle version 11 and lower. For Oracle version 12 and higher OUT parameter will not be generated, and PIPELINE functionality will be used. \\ Possible values - "Yes", "No" or Empty. \\ Default values - "No" or Empty. |
 | **MIGRATE_MEMBERSHIP** | This option controls the way the **Groups** are converted. When MIGRATE_MEMBERSHIP=No then groups are migrated as simple users and default permissions are used for them, E.G.: \\ For SAP ASA to Microsoft SQL Server db_datareader and db_datawriter are specified. \\ The default value is Yes. Possible values - Yes, No.| | **MIGRATE_MEMBERSHIP** | This option controls the way the **Groups** are converted. When MIGRATE_MEMBERSHIP=No then groups are migrated as simple users and default permissions are used for them, E.G.: \\ For SAP ASA to Microsoft SQL Server db_datareader and db_datawriter are specified. \\ The default value is Yes. Possible values - Yes, No.|
-| **TARGET_FILES_GROUPING** | This option controls the way the result SQL files are generated. \\ When data export is switched off and the TARGET_FILES_GROUPING = YES, then separate SQL files are generated each for each object extracted from the source database. \\ If the TARGET_FILES_GROUPING=ALL, then all the generated SQL is stored in one large file.  \\ The default value is empty. Possible values - ALL.| +| **TARGET_FILES_GROUPING** | This option controls the way the result SQL files are generated. \\ When data export is switched off and the TARGET_FILES_GROUPING = YES, then separate SQL files are generated for each object extracted from the source database. \\ If the TARGET_FILES_GROUPING=ALL, then all the generated SQL is stored in one large file.  \\ The default value is empty. Possible values - ALL.| 
-| **CONVERT_GLOBAL_VARIABLES_TO_LOCAL** | This option controls the way global or user variables are converted by SQLWays. \\ When the option is set to Yes, all global variables are converted to local variables declared and used inside the SP or FN only. \\ If the option is set to No, then global variables are converted to their equivalent, automatically generated by SQLWays.  \\ The default value is No. Possible values - Yes, No.| +| **CONVERT_GLOBAL_VARIABLES_TO_LOCAL** | This option controls the way global or user variables are converted by SQLWays. \\ When the option is set to Yes, all global variables are converted to local variables declared and used inside a SP or FN only. \\ If the option is set to No, global variables are converted to their equivalents, automatically generated by SQLWays.  \\ The default value is No. Possible values - Yes, No.| 
-| **PKG_VARIABLES** | This option controls the way global variables are stored in the target database. \\ When the option is set to UNION_BY_PACKAGE, all package variables, that belong to one package, are stored in one table per package, where column names correspond to variable names and values are stored each in its own column. \\ If the option is set to UNION_BY_TYPE, then all global variables are stored in tables, each for its own type group, where variable name is stored as the value of the column with the corresponding variable value in the corresponding row. \\ If the option is set to LOCAL, then all the global variables are converted to local variables. Please use this option carefully to avoid import issues, as not all the source cases can be converted using this option. \\ The default value is UNION_BY_TYPE. Possible values - UNION_BY_TYPE, UNION_BY_PACKAGE and LOCAL.| +| **PKG_VARIABLES** | This option controls the way global variables are stored in the target database. \\ When the option is set to UNION_BY_PACKAGE, all package variables that belong to one package are stored in one table per package, where column names correspond to variable names and all the values are stored in their own columns. \\ If the option is set to UNION_BY_TYPE, all global variables are stored in tables, each for its own type group, where variable name is stored as the value of the column with the corresponding variable value in the corresponding row. \\ If the option is set to LOCAL, all the global variables are converted to local variables. Please use this option carefully to avoid import issues, as not all the source cases can be converted using this option. \\ The default value is UNION_BY_TYPE. Possible values - UNION_BY_TYPE, UNION_BY_PACKAGE and LOCAL.| 
-| **CONVERT_PK_INDEX** | This option controls the way the indexes, created on primary column in DB2, are converted by SQLWays. \\ When the option is set to Yes, the indexes on primary columns are converted to their equivalent. \\ If the option is set to No, then indexes are commented by SQLWays.  \\ The default value is Yes. Possible values - Yes, No. \\ Currently this option works only for DB2 to Oracle migration direction.| +| **CONVERT_PK_INDEX** | This option controls the way the indexes, created on primary column in DB2, are converted by SQLWays. \\ When the option is set to Yes, the indexes on primary columns are converted to their equivalents. \\ If the option is set to No, then indexes are commented by SQLWays.  \\ The default value is Yes. Possible values - Yes, No. \\ Currently this option works only for DB2 to Oracle migration direction.| 
-| **FN_RET_MULTIPLE_VALUES_TO_TABLE_FN** | This option controls the way informix functions, which return multiple values, are converted to MSSQL Server. If this option is set as Yes, SQLWays will convert it as Table Function in MSSQL, if NO - procedure with out parameters. \\ The default value is No. Possible values - Yes, No.| +| **FN_RET_MULTIPLE_VALUES_TO_TABLE_FN** | This option controls the way informix functions which return multiple values are converted to MSSQL Server. If this option is set as Yes, SQLWays will convert them as Table Function in MSSQL, if NO - as procedures with out parameters. \\ The default value is No. Possible values - Yes, No.| 
-| **SW_SEQ_SUFFIX** | This option adds suffix to the sequences generated automatically by Ispirer SQLWays Wizard. Default value is "SWS_". If both options SW_SEQ_SUFFIX and SW_SEQ_PREFIX are empty default suffix("SWS_") and prefix("_ID") for sequences will be used. | +| **SW_SEQ_SUFFIX** | This option adds suffix to the sequences generated automatically by Ispirer SQLWays Wizard. Default value is "SWS_". If both options SW_SEQ_SUFFIX and SW_SEQ_PREFIX are empty, default suffix("SWS_") and prefix("_ID") for sequences will be used. | 
-| **SW_SEQ_PREFIX** | This option adds prefix to the sequences generated automatically by Ispirer SQLWays Wizard. Default value is "_ID". If both options SW_SEQ_SUFFIX and SW_SEQ_PREFIX are empty suffix("SWS_") and prefix("_ID") for sequences will be used default. | +| **SW_SEQ_PREFIX** | This option adds prefix to the sequences generated automatically by Ispirer SQLWays Wizard. Default value is "_ID". If both options SW_SEQ_SUFFIX and SW_SEQ_PREFIX are empty, suffix("SWS_") and prefix("_ID") for sequences will be used by default. | 
-| **SW_TRIG_SUFFIX** | This option adds suffix to the triggers generated automatically by Ispirer SQLWays Wizard. Default value is "SWT_". If both options SW_TRIG_SUFFIX and SW_TRIG_PREFIX are empty default suffix("SWT_") and prefix("_ID") for triggers will be used. | +| **SW_TRIG_SUFFIX** | This option adds suffix to the triggers generated automatically by Ispirer SQLWays Wizard. Default value is "SWT_". If both options SW_TRIG_SUFFIX and SW_TRIG_PREFIX are empty, default suffix("SWT_") and prefix("_ID") for triggers will be used. | 
-| **SW_TRIG_PREFIX** | This option adds suffix to the triggers generated automatically by Ispirer SQLWays Wizard. Default value is "_ID". If both options SW_TRIG_SUFFIX and SW_TRIG_PREFIX are empty suffix("SWT_") and prefix("_ID") for triggers will be used default. | +| **SW_TRIG_PREFIX** | This option adds suffix to the triggers generated automatically by Ispirer SQLWays Wizard. Default value is "_ID". If both options SW_TRIG_SUFFIX and SW_TRIG_PREFIX are empty, suffix("SWT_") and prefix("_ID") for triggers will be used by default. | 
-| **ANSI_QUOTED_IDENTIFIERS** | This option controls how to handle text inside the double quotes. If this option is empty or set to "No", text in double quotes will be identified as a simple string. If this option is set to "Yes" SQLWays will handle text in double quotes as identifier names. \\ Possible values - "Yes", "No" or empty(the same as "No"). Default value - "No" or empty. | +| **ANSI_QUOTED_IDENTIFIERS** | This option controls how to handle the text inside double quotes. If this option is empty or set to "No", the text in double quotes will be identified as a simple string. If this option is set to "Yes" SQLWays will handle the text in double quotes as identifier names. \\ Possible values - "Yes", "No" or empty(the same as "No"). Default value - "No" or empty. | 
-| **TARGET_BL** | This option controls how business logic objects (procedures, functions, triggers, etc.) should be converted - to SQL objects or to Java classes. By default this option is set to "Default" and business logic objects will be converted to SQL objects. If this option is set to "Java" java classes will be generated as a result of conversion. Possible values - "Default" and "Java". | +| **TARGET_BL** | This option controls how business logic objects (procedures, functions, triggers, etc.) should be converted: to SQL objects or to Java classes. By default this option is set to "Default" and business logic objects will be converted to SQL objects. If this option is set to "Java", java classes will be generated as a result of conversion. Possible values - "Default" and "Java". | 
-| **CASCADE_CONSTRAINTS_NO_ACTION** | If there is a referential relationship between a table and the parent row is altered in the parent table, an action, which should be done on child table, can be specified in constraint definition. If you set this option as "Yes", this action will be set to "NO ACTION" in constraint. Default value - "No". Possible values - "Yes", "No". | +| **CASCADE_CONSTRAINTS_NO_ACTION** | If a referential relationship between a table and the parent row is altered in the parent table, an action, which should be performed for child table, can be specified in constraint definition. If you set this option as "Yes", this action will be set to "NO ACTION" in constraint. Default value - "No". Possible values - "Yes", "No". | 
-| **QUOTE_IDENTIFIERS** | This option puts identifier names in quotes in target scripts. Possible values - "Always", empty. Default - empty. |+| **QUOTE_IDENTIFIERS** | This option encloses identifier names in quotes in target scripts. Possible values - "Always", empty. Default - empty. |
 | **SYNONYM_TO_VIEW** | This option controls how Oracle synonyms should be converted to PostgreSQL database. By default CREATE SYNONYM statement will be commented and all the synonyms identifiers will be changed to the original object names. If this option is set to YES, all the synonyms will be converted to views in PostgreSQL. Possible values - "Yes", "No" or empty. Default - "No" or empty. | | **SYNONYM_TO_VIEW** | This option controls how Oracle synonyms should be converted to PostgreSQL database. By default CREATE SYNONYM statement will be commented and all the synonyms identifiers will be changed to the original object names. If this option is set to YES, all the synonyms will be converted to views in PostgreSQL. Possible values - "Yes", "No" or empty. Default - "No" or empty. |
 | **CONVERT_SP_RETSTATUS_OUTPARAM** | If this option is set to "Yes" the source procedure will be converted to the procedure in the target with additional OUT parameter, that will return status of procedure execution. If this option is set to "No", source procedure will be converted to the function with return statement. Possible values - "Yes", "No". | | **CONVERT_SP_RETSTATUS_OUTPARAM** | If this option is set to "Yes" the source procedure will be converted to the procedure in the target with additional OUT parameter, that will return status of procedure execution. If this option is set to "No", source procedure will be converted to the function with return statement. Possible values - "Yes", "No". |
-| **CONVERT_CHECK_CONSTRAINTS** | This option defines whether check constraints should be converted. If this option is set to "Yes", check constraints will be converted. If it is set to "No" - check constraints will not be converted. \\ Possible values - Yes, No. \\ Default value - Yes. | +| **CONVERT_CHECK_CONSTRAINTS** | This option defines whether check constraints should be converted or not. If this option is set to "Yes", check constraints will be converted. If it is set to "No" - check constraints will not be converted. \\ Possible values - Yes, No. \\ Default value - Yes. | 
-| **CONVERT_UNIQUE_CONSTRAINTS** | This option defines whether unique constraints should be converted. If this option is set to "Yes", unique constraints will be converted. If it is set to "No" - unique constraints will not be converted. \\ Possible values - Yes, No. \\ Default value - Yes. | +| **CONVERT_UNIQUE_CONSTRAINTS** | This option defines whether unique constraints should be converted or not. If this option is set to "Yes", unique constraints will be converted. If it is set to "No" - unique constraints will not be converted. \\ Possible values - Yes, No. \\ Default value - Yes. | 
-| **SCHEMA_TO_DATABASE** | This option controls schema names conversion for all specified objects for the migration process. If this option is set to "Yes", converted objects will be created under the database with the same name as the source schema has. In that case, the schema name will be obtained from OUTSCHEMA option. If it is set to "No" - the source database structure will be saved. \\ Possible values - Yes, No. \\ Default value - No. | +| **SCHEMA_TO_DATABASE** | This option controls schema names conversion for all specified objects for the migration process. If this option is set to "Yes", converted objects will be created under the database with the same name as the source schema has. In that case, the schema name will be obtained from OUTSCHEMA option. If it is set to "No", the source database structure will be saved. \\ Possible values - Yes, No. \\ Default value - No. | 
-| **PARTITION_TABLESPACE** | This option controls whether source partition table tablespaces should be converted or no. In case when the option is set into "Yes", source tablespaces for table partitions will be included in migration solution and target definitions of table partitions will contain tablespaces equal to source tablespaces. If the option = "No", tablespaces for table partitions will be ignored. \\ Possible values - Yes, No. \\ Default value - No. | +| **PARTITION_TABLESPACE** | This option controls whether source partition table tablespaces should be converted or not. When the option is set into "Yes", source tablespaces for table partitions will be included in migration solution and target definitions of table partitions will contain tablespaces equal to source tablespaces. If the option = "No", tablespaces for table partitions will be ignored. \\ Possible values - Yes, No. \\ Default value - No. | 
-| **REMOVE_VAR_PREFIX** | This option controls the way the source variable prefix like "@" will be replaced from MS SQL Server, Sybase ASE databases inTO other target databases. In case the option is set to "Yes", the SQLWays will just remove the variable prefix and variable name will be without any additional prefixes. If the option = "No", the SQLWays will remove source prefix with the prefix defined in the VAR_PREFIX option. Default prefix that will be used is "v_". User can specify its own prefix that will be used in conversion. \\ Possible values - Yes, No. \\ Default value - Yes. | +| **REMOVE_VAR_PREFIX** | This option controls the way the source variables from Firebird, MS SQL Server and Sybase ASE databases will be converted into other target databases. \\ Variables in MS SQL Server and Sybase ASE databases could contains prefix like “@”. In case the option is set to “Yes”, SQLWays will just remove the variable prefix so that variable name will not have any additional prefixes. If the option is set to “No”, SQLWays will remove source prefix if exists(for MS SQL Server and Sybase ASE databases) and add the prefix defined in the VAR_PREFIX option. Default prefix that will be used is “v_”. The user can specify his own prefix that will be used during conversion \\ Possible values - Yes, No. \\ Default value - No. | 
-| **VAR_PREFIX** | This option defines what variable prefix will be used in variables when migrating from such databases as MS SQL Server and Sybase ASE. In this option a user can specify its own prefix. \\ Default value - "v_". | +| **VAR_PREFIX** | This option defines which variable prefix will be used in variables when migrating from such databases as Firebird, MS SQL Server and Sybase ASE. In this option the user can specify his own prefix. \\ Default value - "v_". | 
-| **USE_CHAR_LENGTH** | When migrating tables from Oracle to PostgreSQL, Greenplum or Redshift direction, information about the column length is taken from DATA_LENGTH column from ALL_TAB_COLUMNS system table. This column stores information about the number of bytes of CHAR\VARCHAR2 and NCHAR\NVARCHAR2 columns. And if you need to use the number of characters as a length of CHAR\VARCHAR2 and NCHAR\NVARCHAR2 columns, then you need to set this option to "Yes" and our tool will use information from ALL_TAB_COLUMNS from "CHAR_LENGTH" column. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |+| **USE_CHAR_LENGTH** | When migrating tables from Oracle to PostgreSQL, Greenplum or Redshift, information about the column length is taken from DATA_LENGTH column from ALL_TAB_COLUMNS system table. This column stores information about the number of bytes of CHAR\VARCHAR2 and NCHAR\NVARCHAR2 columns. And if you need to use the number of characters as a length of CHAR\VARCHAR2 and NCHAR\NVARCHAR2 columns, you need to set this option to "Yes" and our tool will use information from ALL_TAB_COLUMNS from "CHAR_LENGTH" column. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **USE_SYSTEM_COLUMN_NAME** | This option allows to use system column names when migrating from DB2 database. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **REFCUR_NAME_FOR_RESULT_SETS** | This option allows to control the name of the refcursor OUT parameter name. | 
 +| **CONVERT_INDEXES** | This option defines the types of the indexes that will be converted by SQLWays tool. \\ Possible values - "All", "None", "Unique". \\ Default value - "ALL". | 
 +| **CONVERT_TEMPORARY_TABLES_TO_PERMANENT_TABLES** | This option defines how to convert temporary tables. If this option is set to "No", temporary tables will be converted as is. If this option is set to "Yes", temporary tables will be converted to permanent tables. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **CONVERT_ALL_SP_TO_PACKAGE** | If this option is set to "Yes", all the procedures will be converted to one set of procedures inside one package, when migrating to Oracle. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **START_VALUE_EXTRACTION_WITH_SEQUENCE_INCREMENT** | If this option is set to "Yes", SQLWays tool will extract start value of the sequence as a current value plus increment. Important notification - this option will change the current sequence value in the source Informix database. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **CONVERT_COMMENTS** | This option defines whether the comments inside the sql code should be converted or not. By default this option is set to "Yes" and all the comments are saved. If we set this option to "No", comments will be removed from the sql code. \\ Possible values - "Yes", "No". \\ Default value - "Yes". | 
 +| **EXPORT_CONSTRAINTS_FOR_QUERIES** | This option controls whether the constraints should be converted when performing conversion using the queries. \\ Possible values - "Yes", "No". \\ Default value - "Yes". | 
 +| **CONVERT_MM_TAB** | This option defines how multi-member tables will be converted from DB2 AS 400 into Microsoft SQL Server database. If this option is set to "SINGLE", our tool will try to extract the data from all the members created on this table in DB2 database and load all the extracted data into one table in MSSQL. In that case table in MSSQL will have the same name as original table in DB2. If this option is set to "MULTIPLE", our tool will extract information about the table and data from each member and will create separate tables in MSSQL for each member with the same structure as the original table. It means that in the target database we will have multiple tables with data and with the same name as the corresponding member. \\ Possible values - "SINGLE" or "MULTIPLE". \\ Default value - "SINGLE". | 
 +| **ORACLE_PKG_TO_FN** | This option allows to change package conversion structure logic for Oracle to Greenplum migration direction. By default Oracle packages are converted to sets of Greenplum functions that correspond to source package routines. Package global variables are converted using temporary tables. If the option is set to 'Yes', Oracle package will be converted into one function which takes 1 parameter to pass package routine name and branches package routines logic via IF...ELSE structures. In this case package global variables will be converted to function local variables.\\ Possible values - "Yes", "No". \\ Default value - "Yes". | 
 +| **APP_PARAMS_IN_SQL** | This option defines whether the application parameters are used in source Sybase ASE sql code. If this option is set to "yes" parser will try to find such parameters and leave them as is. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **VARCHAR_PAR_LEN** | When migrating from Oracle to MySQL, you can specify your own length for VARCHAR parameters in procedures and functions. Specified number will be used as a length of VARCHAR parameters in MySQL procedures and functions. | 
 +| **FK_SELECTED_TABLES_ONLY** | This option defines whether to generate Foreign Key constraints that references tables that were not selected for conversion. If this option is set to "Yes" then Foreign Keys will be generated only for tables that were specified for current conversion process. If this option is set to "No", then will be generated all the Foreign Key created on selected tables, even if they refers to the tables that were not selected for conversion. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **PERCENT_AS_COMMENT** | Sybase ASA database 10 version and lower allows to use "%" character as a comment in sql code. To parse and convert such comments in a proper way into the target database we need to set this option to "Yes". If this option will be set to "No" or Empty, "%" will be treated by the tool as modulo operator. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **TEMP_TAB_SCHEMA** | This option defines the schema name for temporary tables. It works only when option "EMPTY_SCHEMA" is set to "No". Implemented for Sybase ASE to Oracle direction only. | 
 +| **CONVERT_SYSTEM_VERSIONED_TABS** | This option defines how to MSSQL convert system versioned tables to PostgreSQL. If this option is set to Yes, then will be generated additional triggers that will emulate the same behavior in PostgreSQL. If this option is empty or set to "No", then system versioned tables will be generated as common tables in PostgreSQL. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **OUTER_JOIN_RETURNS_NULLS** | When migrating to Oracle in JOIN is used varchar column that allows NULLs values and this option is set to Yes, then such column will be placed inside NVL function. If this option is empty or set to "No", then will be used default conversion. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
  
 **Example**: **Example**:
Line 65: Line 100:
 \\ \\
  
-If you have any questions about the supported options or some features that you may need during your migration project, please contact our technical team: **__[[[email protected]]]__**+If you have any questions about the supported options or about any features that you may need for your migration project, please contact our technical team: **__[[[email protected]]]__** 
  
-\\ 
-[[http://www.ispirer.com|Ispirer Home Page]] 
-[[http://www.ispirer.com/products|Ispirer SQLWays Product Page]] 
-[[http://www.ispirer.com/?click=RequestSQLWays&from=IspirerWIKI|Request SQLWays]] 
© 1999-2024, Ispirer Systems, LLC. All Rights Reserved.