Ispirer Ispirer
 

Differences

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

Link to this comparison view

sqlways:command-line:sqlways-ini:sql-server-section [July 31, 2018, 11:57:03 AM]
alexandr.kirpichny
sqlways:command-line:sqlways-ini:sql-server-section [October 05, 2018, 11:44:24 AM] (current)
darya.prikhodkina
Line 8: Line 8:
 ^  Option name  ^ Description  ^  ^  Option name  ^ Description  ^ 
 | **BIN** | Specifies the directory where Microsoft SQL Server utilities like BCP and ISQL are located. | | **BIN** | Specifies the directory where Microsoft SQL Server utilities like BCP and ISQL are located. |
-| **TARGET_VERSION** | Specifies the target version of the MSSQL database. If this option is empty the latest MSSQL database version will be used. Note: According to the version number conversion results may be different.  |+| **TARGET_VERSION** | Specifies the target version of the MSSQL database. If this option is empty the latest MSSQL database version will be used. Note: According to the version number conversion results may differ.  |
 | **SERVER_NAME** | Specifies the server name which is used in generated scripts for the BCP and ISQL utilities (Parameter -S of BCP). | | **SERVER_NAME** | Specifies the server name which is used in generated scripts for the BCP and ISQL utilities (Parameter -S of BCP). |
 | **DATABASE** | Specifies the database name which is used in generated scripts for the BCP and ISQL utilities. | | **DATABASE** | Specifies the database name which is used in generated scripts for the BCP and ISQL utilities. |
-| **USER** | Specifies the user name which is used in generated scripts for the BCP and ISQL utilities (Parameter -U of BCP). To use this option, the option TRUSTED_CONNECTION (see below) must be set to No. | +| **USER** | Specifies the user name which is used in generated scripts for the BCP and ISQL utilities (Parameter -U of BCP). To use this option, set the TRUSTED_CONNECTION option (see below) to No. | 
-| **PWD** | Specifies the user password which is used in generated scripts for the BCP and ISQL utilities (Parameter -P of BCP). To use this option the option TRUSTED_CONNECTION (see below) must be set to No. |+| **PWD** | Specifies the user password which is used in generated scripts for the BCP and ISQL utilities (Parameter -P of BCP). To use this option set the TRUSTED_CONNECTION (see below) option to No. |
 | **TRUSTED_CONNECTION** | Specifies that a trusted connection to Microsoft SQL Server is used in generated scripts for the BCP and ISQL utilities (Parameters -T of BCP and -E of ISQL). When Yes has been chosen in this option, security credentials of the network user are used and a user name (login_id) and a password are not required. Possible values are Yes, No. The default value is No. | | **TRUSTED_CONNECTION** | Specifies that a trusted connection to Microsoft SQL Server is used in generated scripts for the BCP and ISQL utilities (Parameters -T of BCP and -E of ISQL). When Yes has been chosen in this option, security credentials of the network user are used and a user name (login_id) and a password are not required. Possible values are Yes, No. The default value is No. |
 | **MAX_ERRORS** | Specifies the maximum number of errors that can occur before the BCP utility is canceled. Each row that cannot be copied by BCP is ignored and counted as one error (Parameter -m of BCP). The default value is 10. | | **MAX_ERRORS** | Specifies the maximum number of errors that can occur before the BCP utility is canceled. Each row that cannot be copied by BCP is ignored and counted as one error (Parameter -m of BCP). The default value is 10. |
 | **CODE_PAGE** | Specifies a code page of the data in the data file for the BCP utility (Parameter -C of BCP). The following values can be specified for the CODE_PAGE option: \\ * **ACP** - ANSI/Microsoft Windows (ISO 1252). \\ * **OEM** - Default code page used by the client. This is the default code page used by bcp if -C is not specified. \\ * **RAW** - No conversion from one code page to another is taking place. \\ * <value> - Specific code page number, for example, 437. | | **CODE_PAGE** | Specifies a code page of the data in the data file for the BCP utility (Parameter -C of BCP). The following values can be specified for the CODE_PAGE option: \\ * **ACP** - ANSI/Microsoft Windows (ISO 1252). \\ * **OEM** - Default code page used by the client. This is the default code page used by bcp if -C is not specified. \\ * **RAW** - No conversion from one code page to another is taking place. \\ * <value> - Specific code page number, for example, 437. |
-| **int2dec38** | Specifies how to convert Oracle PL/SQL data types INT and INTEGER to Microsoft SQL Server. \\ As the default Oracle PL/SQL data types INT and INTEGER are converted to INT data type. \\ With the option set as YES Oracle PL/SQL data types INT and INTEGER are converted to DECIMAL(38,0) in SQL Server. | +| **int2dec38** | Specifies how to convert Oracle PL/SQL data types INT and INTEGER to Microsoft SQL Server. \\ By default Oracle PL/SQL data types INT and INTEGER are converted to INT data type. \\ With the option set to YES Oracle PL/SQL data types INT and INTEGER are converted to DECIMAL(38,0) in SQL Server. | 
-| **smallint2dec38** | Specifies how to convert Oracle PL/SQL data type SMALLINT to Microsoft SQL Server. \\ As the default Oracle PL/SQL data type SMALLINT is converted to SMALLINT data type. \\ With the option set as YES Oracle PL/SQL data type SMALLINT is converted to DECIMAL(38,0) in Microsoft SQL Server. |+| **smallint2dec38** | Specifies how to convert Oracle PL/SQL data type SMALLINT to Microsoft SQL Server. \\ By default Oracle PL/SQL data type SMALLINT is converted to SMALLINT data type. \\ With the option set to YES Oracle PL/SQL data type SMALLINT is converted to DECIMAL(38,0) in Microsoft SQL Server. |
 | **USE_CONVERT_CHAR_TO_VARCHAR** | This option controls whether to convert CHAR data type to VARCHAR data type while converting to Microsoft SQL Server. The lower limit of CHAR size for which the conversion is required is controlled by **CONVERT_CHAR_TO_VARCHAR** option. The default is No. | | **USE_CONVERT_CHAR_TO_VARCHAR** | This option controls whether to convert CHAR data type to VARCHAR data type while converting to Microsoft SQL Server. The lower limit of CHAR size for which the conversion is required is controlled by **CONVERT_CHAR_TO_VARCHAR** option. The default is No. |
 | **CONVERT_CHAR_TO_VARCHAR** | This option controls the lower limit of CHAR size for which the conversion from CHAR to VARCHAR is required. The optimized default is 20. | | **CONVERT_CHAR_TO_VARCHAR** | This option controls the lower limit of CHAR size for which the conversion from CHAR to VARCHAR is required. The optimized default is 20. |
 | **ROWID_FORMAT** | This option controls the way the ROWID from an Oracle database is being converted to a Microsoft SQL Server database. Possible values are physloc (returns the address of the data in hex format), lockres (returns the address of the data in [File:Page:Slot] format). The default is physlock. | | **ROWID_FORMAT** | This option controls the way the ROWID from an Oracle database is being converted to a Microsoft SQL Server database. Possible values are physloc (returns the address of the data in hex format), lockres (returns the address of the data in [File:Page:Slot] format). The default is physlock. |
-| **SET_NOCOUNT_IN_SP** | If this option is set into ON, SET NOCOUNT ON statement will be added at the beginning of stored procedures and SET NOCOUNT OFF at the end. \\ Possible values - "On", "Off". Default value - "Off". |+| **SET_NOCOUNT_IN_SP** | If this option is set to ON, SET NOCOUNT ON statement will be added to the beginning of stored procedures as well as SET NOCOUNT OFF to the end. \\ Possible values - "On", "Off". Default value - "Off". |
 | **DOUBLE_SIZE_CHARACTERS_DATA_TYPES** | If this option is set to "Yes", SQLWays will double the size of the character columns in the converted tables. \\ Possible values - "Yes", "No" or Empty. Default value - "No" or Empty. | | **DOUBLE_SIZE_CHARACTERS_DATA_TYPES** | If this option is set to "Yes", SQLWays will double the size of the character columns in the converted tables. \\ Possible values - "Yes", "No" or Empty. Default value - "No" or Empty. |
-| **ORIGINAL_LOGIN_WITHOUT_DOMAIN** | This option controls the way how Informix function USER will be converted to MS SQL Server. If this option is set to "Yes", SQLWays will generate SWF_ORIGINAL_LOGIN() function that will remove domain name from the result returned by ORIGINAL_LOGIN() function. If this option is empty or set to "No", ORIGINAL_LOGIN() function will be used. \\ Possible values - "Yes", "No" or Empty. Default value - "No" or Empty. | +| **ORIGINAL_LOGIN_WITHOUT_DOMAIN** | This option controls the way how Informix function USER is converted to MS SQL Server. If this option is set to "Yes", SQLWays will generate SWF_ORIGINAL_LOGIN() function that will remove domain name from the result returned by ORIGINAL_LOGIN() function. If this option is empty or set to "No", ORIGINAL_LOGIN() function will be used. \\ Possible values - "Yes", "No" or Empty. Default value - "No" or Empty. | 
-| **CHECK_DATETIME_DATA** | When during migration from Firebird to MSSQL global data type mapping is used to change conversion TIMESTAMP data type to DATETIME, instead of DATETIME2, the case when in FIREBIRD database in TIMESTAMP columns stored dates before January 1, 1753, for example May 15, 1555And such dates could not be inserted into DATETIME columns in MSSQL. For such cases the option that will check dates stored in such columns can be used. And if the tool will see that value may not be inserted in DATETIME column may appear, then SQLWays will change it to the January 1, 1753” value. \\ Possible values - "Yes", "No" or Empty. Default value - "No" or Empty. | +| **CHECK_DATETIME_DATA** | Applicable when during the migration from Firebird to MSSQL global data type mapping is used to change conversion of TIMESTAMP data type to DATETIME, instead of DATETIME2 and when in FIREBIRD database TIMESTAMP columns contain dates before "January 1, 1753", for example "May 15, 1555"There are cases when such dates cannot be inserted into DATETIME columns in MSSQL. So this option can be used to check the dates stored in such columns. And if the tool sees that value may not be inserted in DATETIME column, then SQLWays will change it to the "January 1, 1753value. For PostgreSQL to MSSQL direction this option checks the range and also cuts the millisecond part of date. \\ Possible values - "Yes", "No" or Empty. Default value - "No" or Empty. | 
-| **MAP_CHAR_TO_NCHAR** | If this option is set to Yes, all CHAR columns with length lower or equal 4000 will be converted to NCHAR in MSSQL. \\ Possible values - "Yes", "No" or empty. Default value - "No" or empty. | +| **MAP_CHAR_TO_NCHAR** | If this option is set to Yes, all CHAR columns with length less or equal to 4000 will be converted to NCHAR in MSSQL. \\ Possible values - "Yes", "No" or empty. Default value - "No" or empty. | 
-| **MAP_VARCHAR_TO_NVARCHAR** | If this option is set to Yes, all VARCHAR columns with length lower or equal 4000 will be converted to NVARCHAR in MSSQL. \\ Possible values - "Yes", "No" or empty. Default value - "No" or empty. | +| **MAP_VARCHAR_TO_NVARCHAR** | If this option is set to Yes, all VARCHAR columns with length less or equal to 4000 will be converted to NVARCHAR in MSSQL. \\ Possible values - "Yes", "No" or empty. Default value - "No" or empty. | 
-| **FN_IDX_TO_IDX_VIEW** | This option defines the way how Oracle function-based indexes will be converted in MSSQL. If this option is set to Yes, function-based indexes will be converted into indexed view in MSSQL. \\ Possible values - "Yes", "No" or empty. Default value - "No" or empty. | +| **FN_IDX_TO_IDX_VIEW** | This option defines the way how Oracle function-based indexes will be converted to MSSQL. If this option is set to Yes, function-based indexes will be converted into indexed views in MSSQL. \\ Possible values - "Yes", "No" or empty. Default value - "No" or empty. | 
-| **HINT** | This option specifies the hint or hints to be used during a bulk import of data into a table in MSSQL Database. All the possible hints are supported in our toolkit. More information about the hints supported by MSSQL BCP utility you can find here: [[https://docs.microsoft.com/en-us/sql/tools/bcp-utility?view=sql-server-2017#h|MSSQL Server BCP Hints]]. \\ Possible values: Hints supported by MSSQL Server. \\ Default value: Empty. |+| **HINT** | This option specifies the hint or hints to be used during a bulk import of data into a table in MSSQL Database. All possible hints are supported in our toolkit. More information about the hints supported by MSSQL BCP utility can be found here: [[https://docs.microsoft.com/en-us/sql/tools/bcp-utility?view=sql-server-2017#h|MSSQL Server BCP Hints]]. \\ Possible values: Hints supported by MSSQL Server. \\ Default value: Empty. |
 | **MS_QUOTED_IDENTIFIER** | This option defines the way how MSSQL native utilities (sqlcmd.exe and bcp.exe) will treat quoted delimiters and data. If this option is set to "Yes" identifiers should be delimited with double quotes and literals must be delimited with single quotation marks. When this option is set to "No", then only brackets [] can be used to delimit identifiers and double quotation marks will be used to delimit character strings. \\ Possible values - "Yes", "No" or empty. \\ Default value - "No" or empty. | | **MS_QUOTED_IDENTIFIER** | This option defines the way how MSSQL native utilities (sqlcmd.exe and bcp.exe) will treat quoted delimiters and data. If this option is set to "Yes" identifiers should be delimited with double quotes and literals must be delimited with single quotation marks. When this option is set to "No", then only brackets [] can be used to delimit identifiers and double quotation marks will be used to delimit character strings. \\ Possible values - "Yes", "No" or empty. \\ Default value - "No" or empty. |
 | **PARTITION_ENABLE** | This option controls whether partition tables conversion is required. When option is set to 'Yes', table partitioning logic will be migrated and additional partition function and partition scheme will be created. Otherwise, partitioning logic will be omitted. \\ Possible values - "Yes", "No" or empty. \\ Default value - "No" or empty. | | **PARTITION_ENABLE** | This option controls whether partition tables conversion is required. When option is set to 'Yes', table partitioning logic will be migrated and additional partition function and partition scheme will be created. Otherwise, partitioning logic will be omitted. \\ Possible values - "Yes", "No" or empty. \\ Default value - "No" or empty. |
 | **PARTITION_FILEGROUP** | The option sets filegroups names for the conversion solution for table partitioning. It can take any value which is the name of filegroup. PRIMARY filegroup is used by default. \\ Please, take into account that filegroups will not be created automatically during the migration. Please, create required filegroups manually.  \\ Default value - "PRIMARY" or empty. | | **PARTITION_FILEGROUP** | The option sets filegroups names for the conversion solution for table partitioning. It can take any value which is the name of filegroup. PRIMARY filegroup is used by default. \\ Please, take into account that filegroups will not be created automatically during the migration. Please, create required filegroups manually.  \\ Default value - "PRIMARY" or empty. |
 | **USE_SOURCE_FILEGROUP_NAMES** | If the option is set to 'Yes', source filegroups/tablespaces names will be used as filegroups names for table partitioning solution in target MSSQL database. Otherwise, filegroups names will be controlled by PARTITION_FILEGROUP option.\\ Possible values - "Yes", "No" or empty. \\ Default value - "No" or empty. | | **USE_SOURCE_FILEGROUP_NAMES** | If the option is set to 'Yes', source filegroups/tablespaces names will be used as filegroups names for table partitioning solution in target MSSQL database. Otherwise, filegroups names will be controlled by PARTITION_FILEGROUP option.\\ Possible values - "Yes", "No" or empty. \\ Default value - "No" or empty. |
-| **USE_ACTIVE_DIRECTORY** | This option switches authentication mechanism to use ACTIVE DIRECTORY authentication. Thus, if this option is set to “Yes”, option -G will be added in the commands to SQLCMD and BCP utilities. The -G switch requires at least sqlcmd version 13.1. \\ Possible values - "Yes", "No" or empty. \\ Default value - "No" or empty. |+| **USE_ACTIVE_DIRECTORY** | This option switches authentication mechanism to use ACTIVE DIRECTORY authentication. Thus, if this option is set to “Yes”, option -G will be added to the commands in SQLCMD and BCP utilities. The -G switch requires at least sqlcmd version 13.1. \\ Possible values - "Yes", "No" or empty. \\ Default value - "No" or empty. |
 | **BATCH_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. | | **BATCH_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. |
-| **CASE_SENSITIVE_COLLATION** | This option check object names case. If this option is set to "Yes", our tool will check the object names taking into account name case. If two objects have the same names and they are written in the same way, for example 'Tab' and 'Tab', in that case suffix will be added to one of the objects. If there are two objects with the same names, but they are written in different manner, for example 'Tab' and 'TAB', in that case no suffix will be added, as this option is set to "Yes". \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |+| **CASE_SENSITIVE_COLLATION** | This option checks object names case. If this option is set to "Yes", our tool will check the object names taking into account name case. If two objects have the same names and they are written in the same way, for example 'Tab' and 'Tab', suffix will be added to one of the objects. If there are two objects with the same names, but written in different manner, for example 'Tab' and 'TAB', no suffix will be added, as this option is set to "Yes". \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |
 | **TABLE_FILEGROUP** | This option defines FILGROUP for tables. | | **TABLE_FILEGROUP** | This option defines FILGROUP for tables. |
 | **INDEX_FILEGROUP** | This option defines FILGROUP for indexes. | | **INDEX_FILEGROUP** | This option defines FILGROUP for indexes. |
sqlways/command-line/sqlways-ini/sql-server-section.1533038223.txt.gz · Last modified: July 31, 2018, 11:57:03 AM by alexandr.kirpichny
 
© 1999-2018, Ispirer Systems Ltd.
All Rights Reserved.  Privacy Statement