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 [September 04, 2018, 12:39:56 PM] (current)
alexandr.kirpichny
Line 29: Line 29:
 | **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. |
 | **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 54:
 | **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 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. |
  
 **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