Ispirer Ispirer
 

Differences

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

Link to this comparison view

sqlways:command-line:sqlways-ini:ddl-section [July 12, 2018, 01:42:32 PM]
alexandr.kirpichny
sqlways:command-line:sqlways-ini:ddl-section [October 26, 2018, 11:57:04 AM] (current)
darya.prikhodkina [Sqlways.ini File - Section [DDL]]
Line 8: Line 8:
 ^  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. |
 +| **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 only available if the target database is Oracle and GENERATE_DROP_TABLE is set to Yes. The default value is 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_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. |
Line 27: Line 39:
 | **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 - 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_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 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_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. |
 +| **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 first of all deletes all consonants 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 consonants characters. \\ The default value is No. Possible values - Yes, No. |
 +| **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 will delete consonants characters and until the identifier's length is equal to the maximum length. If No is specified, SQLWays immediately trims all the consonants characters. \\ The default value is No. Possible values - Yes, No. |
 +| **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 will trim 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 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. | | **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. |
 | **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. | | **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. |
-| **CONVERT_PACKAGE_TO_SCHEMA** | This option is used to convert the Package name as the schema from an Oracle database. \\ It is required to 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. \\ It is required to 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. \\ It is required to set this option to Yes to get it work. | | **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. |
 | **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.|
Line 54: Line 71:
 | **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 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. |
-| **REMOVE_VAR_PREFIX** | This option controls the way the source variable prefix like "@" from MS SQL Server, Sybase ASE databases will be replaced in other target databases. In case when the option is set into "Yes", SQLWays will just remove the variable prefix and variable name will be without any additional prefixes. If the option = "No", 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 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. | 
-| **VAR_PREFIX** | This option defines what variable prefix will be used in variables when migrating from such databases like MS SQL Server and Sybase ASE. In this option user can specify its own prefix. \\ Default value - "v_". |+| **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 user can specify its own prefix. \\ Default value - "v_". | 
 +| **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 the 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 a 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 current value plus increment. Important notification - using 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. 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 doing 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 date 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 the same name as corresponding member. \\ Possible values - "SINGLE" or "MULTIPLE". \\ Default value - "SINGLE". | 
  
 **Example**: **Example**:
sqlways/command-line/sqlways-ini/ddl-section.1531402952.txt.gz · Last modified: July 12, 2018, 01:42:32 PM by alexandr.kirpichny
 
© 1999-2018, Ispirer Systems Ltd.
All Rights Reserved.  Privacy Statement