Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
guides:migration-toolkit:command-line:sqlways-ini:msazuresql-section [2019/10/18 11:15]
darya.prikhodkina
guides:migration-toolkit:command-line:sqlways-ini:msazuresql-section [2019/11/01 08:39]
alexandr.kirpichny
Line 7: Line 7:
 | **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, 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 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 the option TRUSTED_CONNECTION (see below) must be set to "No". | 
-| **TRUSTED_CONNECTION** | Specifies that a trusted connection to Microsoft Azure SQL Database 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 Azure SQL Database is used in generated scripts for the BCP and ISQL utilities (Parameters -T of BCP and -E of ISQL). When "Yes" is specified, 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 this 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 this 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. |
 | **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 should be delimited with single quotation marks. When this option is set to "​No",​ 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 should be delimited with single quotation marks. When this option is set to "​No",​ 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. |
Line 19: Line 19:
 | **TABLE_FILEGROUP** | This option defines FILEGROUP for tables. ​  | | **TABLE_FILEGROUP** | This option defines FILEGROUP for tables. ​  |
 | **INDEX_FILEGROUP** | This option defines FILEGROUP for indexes. ​  | | **INDEX_FILEGROUP** | This option defines FILEGROUP for indexes. ​  |
 +| **FK_DEL_CASCADE_SET_NULL_TO_TRIG** | This option defines how to convert ON DELETE CASCADE and ON DELETE SET NULL foreign key options from Firebird database to MSSQL. If it is set to Yes, then ON DELETE CASCADE and ON DELETE SET NULL foreign key options will be converted into a trigger that emulates the same behavior as in Firebird. |
 +| **FK_UPD_CASCADE_SET_NULL_TO_NO_ACT** | This option defines how to convert ON UPDATE CASCADE and ON UPDATE SET NULL foreign key options from Firebird database to MSSQL. If it is set to Yes, then ON UPDATE CASCADE and ON UPDATE SET NULL foreign key options will be converted into ON UPDATE NO ACTION in Microsoft SQL Server. |
  
 **Example**:​ **Example**:​