Differences

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

--- guides:migration-toolkit:command-line:sqlways-ini:sql-server-section [2019/11/16 11:01]
darya.prikhodkina
+++ guides:migration-toolkit:command-line:sqlways-ini:sql-server-section [2023/06/30 12:45] (current)
vladimir.gribok
@@ Line 1: / Line 1: @@
+** About Ispirer Systems **
+[[https://www.ispirer.com|Ispirer Home Page]]
+[[https://www.ispirer.com/products/database-migration|Database Migration]]
+[[https://www.ispirer.com/application-conversion|Application Conversion]]
+[[https://www.ispirer.com/download|Downloads]]
+----
 ====== Sqlways.ini File - Section [MSSQL] ======
@@ Line 38: / Line 45: @@
 | **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 - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |
 | **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 - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |
+| **USE_CURSORS_IN_TRIGGERS** | If it is set to “No”, then cursor usage inside Triggers will not be converted. If this option is set to No or empty, will be used default conversion. \\ Possible values - “Yes”, “No” or Empty. \\ Default value - “No” or Empty. |
+| **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 “Yes” and table, generator and a trigger that insert new value of generator into a table column were selected for a conversion, trigger will be commented and IDENTITY option will be added to a column in a table. If this option is set to “No”, default conversion will be used. \\ Possible values - “Yes”, “No” or Empty. \\ Default value - “No” or Empty. |
+| **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 “Yes”, then extents will be converted to sparse columns and additional COLUMN_SET column will be generated. This option can be used when number of columns and extents is greater than 1000. \\ Possible values - “Yes”, “No” or Empty. \\ Default value - “No” or Empty. |
+| **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:\\Users\\Documents\\Ispirer\\pr.xml \\ where the content of the pr.xml file is: \\ <Procedures> \\ <Procedure Name=“sproc1” /> \\ <Procedure Name=“sproc2” /> \\ </Procedures> |
+| **CONVERT_SP_WITH_OUTPUT_PARAMS** | Option contains the path to a file that contains a list of procedures that will be converted with the following changes: \\ 1) If a stored procedure does not use RETURN WITH RESUME, the converted SQL Server SP will have a set of output parameters created with default of NULL. Additionally, a new parameter called @SWV_Output_Set will be created with default value of 1. If @SWV_Output_Set = 1, then the stored procedure would return the data in a select statement. If not, the output parameters would communicate the result back to the caller. \\ 2) If a stored procedure uses RETURN WITH RESUME, then the caller stored procedure will continue to create a temp table to transport the result back to the caller. Additionally, a new parameter called @SWV_Output_Set will be created with default value of 1. If @SWV_Output_Set = 1, then the stored procedure would return the data in a select statement without inserting into a temp table first. \\ Default value - Empty. \\ [[samples:options-examples #[Usage example]:CONVERT_SP_WITH_OUTPUT_PARAMS|Usage example]]. |
+| **PROCEDURE_WITH_OUTPUT_PARAMS** | Option defines the way procedures will be converted for MSSQL. If the option set to "Yes", then the procedure will have a set of output parameters created with default NULL values. If the option set to "No", the converted procedure will use the temporary table instead of output parameters in order to insert result set into it and then select them from that table. \\ Possible values - "Yes", "No", Empty. \\ Default value - "Yes". [[samples:options-examples #[Usage example]:PROCEDURE_WITH_OUTPUT_PARAMS|Usage example]].|
 **Example**:
@@ Line 46: / Line 60: @@
 \\
-----
-=== More about Ispirer Systems ===
-[[https://www.ispirer.com|Ispirer Home Page]]
-[[https://www.ispirer.com/products/database-migration|Database Migration]]
-[[https://www.ispirer.com/application-conversion|Application Conversion]]
-[[https://www.ispirer.com/download|Downloads]]