Ispirer Ispirer
 

Differences

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

Link to this comparison view

sqlways:command-line:sqlways-ini:ddl-section [May 03, 2019, 08:18:48 AM]
darya.prikhodkina
sqlways:command-line:sqlways-ini:ddl-section [May 24, 2019, 12:10:16 PM] (current)
alexandr.kirpichny
Line 84: Line 84:
 | **CONVERT_MM_TAB** | This option defines how multi-member tables will be converted from DB2 AS 400 into Microsoft SQL Server database. If this option is set to "SINGLE", our tool will try to extract the data from all the members created on this table in DB2 database and load all the extracted data into one table in MSSQL. In that case table in MSSQL will have the same name as original table in DB2. If this option is set to "MULTIPLE", our tool will extract information about the table and data from each member and will create separate tables in MSSQL for each member with the same structure as the original table. It means that in the target database we will have multiple tables with data and with the same name as the corresponding member. \\ Possible values - "SINGLE" or "MULTIPLE". \\ Default value - "SINGLE". | | **CONVERT_MM_TAB** | This option defines how multi-member tables will be converted from DB2 AS 400 into Microsoft SQL Server database. If this option is set to "SINGLE", our tool will try to extract the data from all the members created on this table in DB2 database and load all the extracted data into one table in MSSQL. In that case table in MSSQL will have the same name as original table in DB2. If this option is set to "MULTIPLE", our tool will extract information about the table and data from each member and will create separate tables in MSSQL for each member with the same structure as the original table. It means that in the target database we will have multiple tables with data and with the same name as the corresponding member. \\ Possible values - "SINGLE" or "MULTIPLE". \\ Default value - "SINGLE". |
 | **ORACLE_PKG_TO_FN** | This option allows to change package conversion structure logic for Oracle to Greenplum migration direction. By default Oracle packages are converted to sets of Greenplum functions that correspond to source package routines. Package global variables are converted using temporary tables. If the option is set to 'Yes', Oracle package will be converted into one function which takes 1 parameter to pass package routine name and branches package routines logic via IF...ELSE structures. In this case package global variables will be converted to function local variables.\\ Possible values - "Yes", "No". \\ Default value - "Yes". | | **ORACLE_PKG_TO_FN** | This option allows to change package conversion structure logic for Oracle to Greenplum migration direction. By default Oracle packages are converted to sets of Greenplum functions that correspond to source package routines. Package global variables are converted using temporary tables. If the option is set to 'Yes', Oracle package will be converted into one function which takes 1 parameter to pass package routine name and branches package routines logic via IF...ELSE structures. In this case package global variables will be converted to function local variables.\\ Possible values - "Yes", "No". \\ Default value - "Yes". |
 +| **APP_PARAMS_IN_SQL** | This option defines whether the application parameters are used in source Sybase ASE sql code. If this option is set to "yes" parser will try to find such parameters and leave them as is. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. |
 +| **VARCHAR_PAR_LEN** | When migrating from Oracle to MySQL, you can specify your own length for VARCHAR parameters in procedures and functions. Specified number will be used as a length of VARCHAR parameters in MySQL procedures and functions. |
  
  
sqlways/command-line/sqlways-ini/ddl-section.1556871528.txt.gz · Last modified: May 03, 2019, 08:18:48 AM by darya.prikhodkina
 
© 1999-2019, Ispirer Systems Ltd.
All Rights Reserved.  Privacy Statement