Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
sqlways:command-line:sqlways-ini:data-section [February 05, 2020, 03:05:19 PM] alexandr.kirpichnysqlways:command-line:sqlways-ini:data-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 [DATA] ====== ====== Sqlways.ini File - Section [DATA] ======
  
Line 24: Line 24:
 | **CORRECT_24H_TIME** | This option changes the time value from "24:00:00" to the time specified in the option for TIME columns when migrating from DB2 database to other databases (for example Oracle and MSSQL Server). If this option is set to Yes, 23:59:59 will be used in the target database.\\ Default value for this option is NO. Possible values - Yes, No, exact time value (for example, 23:45:47). | | **CORRECT_24H_TIME** | This option changes the time value from "24:00:00" to the time specified in the option for TIME columns when migrating from DB2 database to other databases (for example Oracle and MSSQL Server). If this option is set to Yes, 23:59:59 will be used in the target database.\\ Default value for this option is NO. Possible values - Yes, No, exact time value (for example, 23:45:47). |
 | **CORRECT_24H_TIMESTAMP** | This option changes the time value from "24:00:00" to the time specified in the option for TIMESTAMP columns when migrating from DB2 database to other databases (for example Oracle and MSSQL Server). If this option is set to Yes, will be used 23:59:59.999999 in target database.\\ Default value for this option is NO. Possible values - Yes, No, exact time value (for example, 23:45:47). | | **CORRECT_24H_TIMESTAMP** | This option changes the time value from "24:00:00" to the time specified in the option for TIMESTAMP columns when migrating from DB2 database to other databases (for example Oracle and MSSQL Server). If this option is set to Yes, will be used 23:59:59.999999 in target database.\\ Default value for this option is NO. Possible values - Yes, No, exact time value (for example, 23:45:47). |
-| **CASESENSITIVE_DATA_IN_FK_COL** | MSSQL foreign key on char columns treats values in case insensitive mode. In Oracle such behavior is not allowedSo this option will allow to extract data from referenced columns in specific case. If this option is set to Lower, data will be extracted in lower case. If Upper is specified it will be extracted in upper case. If this option is empty or unset, data will be extracted as is. \\ The default value is Empty. Possible values - YesNoEmpty.|+| **CASESENSITIVE_DATA_IN_FK_COL** | By default, MSSQL Server is case-insensitive and processes the values of string columns that are included in foreign keys, in case-insensitive mode. This behavior is unacceptable in Oracle.\\ Thus, this option allows you to extract data from the referenced columns in specific case.\\ If this option is set to Upperthe data will be extracted in uppercase.\\ If Lower is specifiedit will be extracted in lowercase.\\ If this option is empty or not setthe data will be extracted as is.\\ Possible values are: UpperLower(empty).\\ The default value is (empty).|
 | **BOOLEAN_REPRESENTATION** | This option controls the way boolean values will be converted in the target database. Possible values "Y/N", "T/F" or "1/0". If you set "Y/N", "Y" or "N" values will be used; if you set "T/F", "T" or "F" values will be used; if this option is set to "1/0", then "1" and "0" will be used for boolean values. | | **BOOLEAN_REPRESENTATION** | This option controls the way boolean values will be converted in the target database. Possible values "Y/N", "T/F" or "1/0". If you set "Y/N", "Y" or "N" values will be used; if you set "T/F", "T" or "F" values will be used; if this option is set to "1/0", then "1" and "0" will be used for boolean values. |
 | **IFMX_ROWID_IN_BLOBFILE_NAME** | This option adds ROWID to the file name where blob data will be placed after the Export process. If this option is set to "Yes", ROWID number will be added to the file name. If this option is set to "No" or empty, ROWID number will not be added. \\ This option can be applied only for Informix as a source database. Possible values - "Yes", "No" or empty. Default value - "No" or empty. | | **IFMX_ROWID_IN_BLOBFILE_NAME** | This option adds ROWID to the file name where blob data will be placed after the Export process. If this option is set to "Yes", ROWID number will be added to the file name. If this option is set to "No" or empty, ROWID number will not be added. \\ This option can be applied only for Informix as a source database. Possible values - "Yes", "No" or empty. Default value - "No" or empty. |
Line 43: Line 43:
 | **REVERSE_BLOCK_NAMES** | If this option is set to "Yes", block names that start with numbers will be changed and numbers will be placed at the end of the block names. If this option is set to "No" - names will be left as is. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | | **REVERSE_BLOCK_NAMES** | If this option is set to "Yes", block names that start with numbers will be changed and numbers will be placed at the end of the block names. If this option is set to "No" - names will be left as is. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |
 | **COMP_FORMATTING** | This option defines the conversion of COMP clause for items. If it is set to "Yes" COMP clause will be converted. If it is set to "No" - COMP clause will be removed from conversion when migrating from Cobol to Oracle. \\ Possible values - "No","Yes" or Empty. \\ Default value - "Yes" or Empty. | | **COMP_FORMATTING** | This option defines the conversion of COMP clause for items. If it is set to "Yes" COMP clause will be converted. If it is set to "No" - COMP clause will be removed from conversion when migrating from Cobol to Oracle. \\ Possible values - "No","Yes" or Empty. \\ Default value - "Yes" or Empty. |
-| **CONVERT_GUID_BIN_ENCODING** | This option defines whether the conversion of binary encoding of uniqueidentifier values should be performed or not. If this option is set to "Yesand in source database value has Little-endian encoding then value should be converted into Big-Endian encoding. If in source is used Big-Endianthen it will be converted to Little-Endian encoding. If it is set to "Noor Empty - source value will be migrated as is. \\ This option works only for Microsoft SQL Server to PostgreSQL migration directionFor other migration direction it should be extended. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |+| **CHAR_DATA_CASE** | This option defines the case of string data. If this option is set to "LOWER", data will be converted to a lower case. If it is set to "UPPER"data will be converted to upper case. If this option is not set, data will be migrated as is. \\  Possible values - "Upper", "LOWER", Empty. \\ Default value - Empty. | 
 +| **TRIM_TRAILING_BLANKS_IN_CHAR** | If this option is set to "Yes", trailing blanks are removed from the string data. If this option is not set, data will be migrated as is. \\  Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **DEP_ON_DATA_CUT** | This option controls the usage of data cut conditions for referenced tables. If this option is set to "Yes", data cut conditions will be used for table for which this condition was specified and for tables that depend on this tableIf this option is set to "No", data cut conditions will be used only for table where such conditions were specified. \\  Possible values - "No", "Yes" or Empty. \\ Default value - "Yes" or Empty. |
  
  
Line 58: Line 60:
 If you have any questions about the supported options or any features that you may need in your migration project, please contact our technical team: **__[[[email protected]]]__** If you have any questions about the supported options or any features that you may need in 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.