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 [May 28, 2019, 02:20:07 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] ======
  
Line 71: 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 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. | | **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 and Sybase ASE databases into other target databases. 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 with 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 - 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 which variable prefix will be used in variables when migrating from such databases as MS SQL Server and Sybase ASE. In this option the user can specify his 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, 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_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. | | **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. |
Line 87: Line 87:
 | **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. | | **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. | | **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. |
  
  
Line 98: Line 102:
 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]]]__** 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.