Differences

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

Link to this comparison view

guides:migration-toolkit:command-line:sqlways-ini:sybase-section [2019/06/11 00:26]
127.0.0.1 external edit
guides:migration-toolkit:command-line:sqlways-ini:sybase-section [2019/11/16 10:03] (current)
darya.prikhodkina
Line 2: Line 2:
 ====== Sqlways.ini File - Section [SYBASE] ====== ====== Sqlways.ini File - Section [SYBASE] ======
  
-This article describes sqlways.ini file [SYBASE] section and the options it contains. ​+This article describes sqlways.ini file'​s ​[SYBASE] section and the options it contains. ​
 ^  Option name  ^ Description ​ ^  ^  Option name  ^ Description ​ ^ 
-| **BIN** | Specifies the directory where the Sybase utilities like BCP and ISQL are located. | +| **BIN** | Specifies the directory where Sybase utilities like BCP and ISQL are located. | 
-| **TARGET_VERSION** | Specifies the target version of the Sybase database. If this option is empty the latest Sybase database version will be used. \\ Note: According to the version number conversion results may be different. |+| **TARGET_VERSION** | Specifies the target version of Sybase database. If this option is empty the latest Sybase database version will be used. \\ Note: According to the version number conversion results may differ. |
 | **SERVER_NAME** | Specifies the server name that is used in generated scripts for the BCP and ISQL utilities (Parameter -S). | | **SERVER_NAME** | Specifies the server name that is used in generated scripts for the BCP and ISQL utilities (Parameter -S). |
 | **DATABASE** | Specifies the database name that is used in generated scripts for the BCP and ISQL utilities. | | **DATABASE** | Specifies the database name that is used in generated scripts for the BCP and ISQL utilities. |
Line 11: Line 11:
 | **USER** | Specifies the user name that is used in generated scripts for the BCP and ISQL utilities (Parameter -U). | | **USER** | Specifies the user name that is used in generated scripts for the BCP and ISQL utilities (Parameter -U). |
 | **PWD** | Specifies the user password that is used in generated scripts for the BCP and ISQL utilities (Parameter -P). | | **PWD** | Specifies the user password that is used in generated scripts for the BCP and ISQL utilities (Parameter -P). |
-| **TEMP_TAB_INDEXED_ALWAYS** | This option is used for SybaseASE to SybaseASE, when the detection for Cartesian Product works. If this option is specified as yes, all the joins with temporary tables ​are  ​treated as indexed. So no Cartesian ​is detected in this case. Otherwise the Cartesian ​is detected if there is no information about the indexes created upon the temporary tables used in DML statement. |+| **TEMP_TAB_INDEXED_ALWAYS** | This option is used for SybaseASE to SybaseASE, when the detection for Cartesian Product works. If this option is specified as "​Yes"​, all the joins with temporary tables ​will be treated as indexed. So no Cartesian ​will be detected in this case. Otherwise the Cartesian ​will be detected if there is no information about the indexes created upon the temporary tables used in DML statement. |
 | **CLIENT_SIDE_CHARACTER_SET_CONVERSION** | This option specifies client-side character set conversion for the BCP utility (Parameter -Y). \\ Possible values: "​Yes",​ "​No"​. Default value is "​No"​. | | **CLIENT_SIDE_CHARACTER_SET_CONVERSION** | This option specifies client-side character set conversion for the BCP utility (Parameter -Y). \\ Possible values: "​Yes",​ "​No"​. Default value is "​No"​. |
 | **CLIENT_SIDE_PWD_ENCRYPTION** | Specifies the client-side password encryption to the ISQL and BCP utilities commands (Parameter -X). \\ Possible values: "​Yes",​ "​No"​. Default value is "​No"​. | | **CLIENT_SIDE_PWD_ENCRYPTION** | Specifies the client-side password encryption to the ISQL and BCP utilities commands (Parameter -X). \\ Possible values: "​Yes",​ "​No"​. Default value is "​No"​. |
 | **PREFETCH_SIZE** | Specifies the number of rows per batch of data copied. By default, bcp copies n rows in one batch, where n is equal to the batch size. Batch size applies only when you are bulk copying in; it has no effect on bulk copying out. The smallest number bcp accepts for batchsize is 1. The largest number bcp accepts for batchsize is 2147483647L. | | **PREFETCH_SIZE** | Specifies the number of rows per batch of data copied. By default, bcp copies n rows in one batch, where n is equal to the batch size. Batch size applies only when you are bulk copying in; it has no effect on bulk copying out. The smallest number bcp accepts for batchsize is 1. The largest number bcp accepts for batchsize is 2147483647L. |
-| **IDENTIFIER_DELIMITER** | This option defines identifier delimiter that will be used in a query, ​that is used to get data from Sybase database. For more details about this option, please contact our technical support team [[[email protected]]] |+| **IDENTIFIER_DELIMITER** | This option defines identifier delimiter that will be used in a query, ​which is used to get data from Sybase database. For more details about this option, please contact our technical support team [[[email protected]]] |