Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sqlways:command-line:sqlways-ini:sql-server-section [November 06, 2019, 10:37:18 AM] – alexandr.kirpichny | sqlways:command-line:sqlways-ini:sql-server-section [May 31, 2023, 05:28:08 PM] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| \\ | \\ | ||
| - | [[http:// | + | [[https:// |
| - | [[http:// | + | [[https:// |
| - | [[http:// | + | [[https:// |
| ====== Sqlways.ini File - Section [MSSQL] ====== | ====== Sqlways.ini File - Section [MSSQL] ====== | ||
| Line 41: | Line 41: | ||
| | **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. \\ Possible values - " | | **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. \\ Possible values - " | ||
| | **USE_SCOPE_IDENTITY** | This option defines how to convert @@identity global variable when migrating from Sybase Adaptive Server Anywhere to Microsoft SQL Server. If it is set to Yes, then @@identity will be converted to SCOPE_IDENTITY() in Microsoft SQL Server. If this option is set to No, then @@identity global variable will be left as is in MS SQL. \\ Possible values - " | | **USE_SCOPE_IDENTITY** | This option defines how to convert @@identity global variable when migrating from Sybase Adaptive Server Anywhere to Microsoft SQL Server. If it is set to Yes, then @@identity will be converted to SCOPE_IDENTITY() in Microsoft SQL Server. If this option is set to No, then @@identity global variable will be left as is in MS SQL. \\ Possible values - " | ||
| + | | **USE_CURSORS_IN_TRIGGERS** | If it is set to " | ||
| + | | **SEL_INTO_TMP_TAB_TO_INSERT** | This option defines the list of procedures where SELECT INTO TEMP TABLE statement will be converted into separate CREATE TEMP TABLE and INSERT INTO statements. In this options should be specified a path to a file with the names of the objects. This option works only for Informix to Microsoft SQL Server migration direction. | | ||
| + | | **SEQUENCE_TO_IDENTITY** | This option defines the conversion of a trigger that insert new generator value into a column only. If this option is set to " | ||
| + | | **EXTENT_TO_SPARSE** | This option defines the conversion of extent columns from Progress to SQL Server. When this option is set to No or Empty, will be used default conversion when each extent is converted into a separate column in SQL Server and for each Progress extent column is generated a computed column in target. If this option is set to " | ||
| + | | **CONVERT_SP_TO_SP** | The option is responsible for ensuring that objects that can be converted to functions are still converted to procedures. The value of the option specifies the path to the file in which objects names that have to be converted as procedures are specified as an XML structure, e.g. CONVERT_SP_TO_SP=C: | ||
| + | |||
| Line 49: | Line 55: | ||
| CONVERT_CHAR_TO_VARCHAR=10 | CONVERT_CHAR_TO_VARCHAR=10 | ||
| - | \\ | + | |
| - | [[http:// | + | |
| - | [[http:// | + | |
| - | [[http:// | + | |