Ispirer Ispirer
 

Differences

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

Link to this comparison view

sqlways:command-line:sqlways-ini:wizard_common-section [October 12, 2018, 01:54:58 PM]
alexandr.kirpichny
sqlways:command-line:sqlways-ini:wizard_common-section [January 24, 2019, 01:48:43 PM] (current)
darya.prikhodkina
Line 5: Line 5:
 ====== Sqlways.ini File - Section [_WZD_COMMON] ====== ====== Sqlways.ini File - Section [_WZD_COMMON] ======
  
-This article describes sqlways.ini file [_WZD_COMMON] section and the options it contains. +This article describes sqlways.ini file's [_WZD_COMMON] section and the options it contains. 
 ^  Option name  ^ Description  ^  ^  Option name  ^ Description  ^ 
-| **GENERATE_IMPORT_SCRIPTS** | If this option is set to Yes, SQLWays Wizard will generate all the files required for making import into the target database. Such files as ctl, .ldi and .bat files. If this option is set to "No", such files will not be generated. Also this option can be set in the SQLWays Wizard tool, on the "Choose a Target Database" page. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". | +| **RUN_IMPORT_REMOTLY** | This option defines whether the import process will be run from a remote machine. It means that all the generated files will be copied to another, remote machine. And import will be run from that machine. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No". | 
-| **REPLACE_NOT_ALLOWED_CHARS_FPOS** | Some databases identifier names could contain specific characters that may not be allowed in the target database. This option was created in order to replace such characters only from first position. Character that will replace not allowed characters should be specified in this option. |+| **AUTOSTART_IMPORT** | This option defines whether the import process will be run automatically after the conversion. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No". | 
 +| **USE_IMPORT_LOG_ANALYZER** | If this option is set to "Yes", SQLWays Wizard tool will try to analyze the import process according the the information in the import log file, and generate summary information at the end of the import log file. Can be used only for MySQL database as a target. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No". | 
 +| **PRECACHE_OBJECTS** | If this option is set to "Yes", SQLWays Wizard tool will try to use cache technology and select information about all the tables in database using only one sql query. If this query is set to "No", separate queries will be used to get information about each table. This option will work only when the number of tables specified for conversion is larger than the number provided in the PRECACHE_TABLES_COUNT option. The performance can be improved only when the number specified in the PRECACHE_TABLES_COUNT option is more than 51% of all the tables in the database. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No". | 
 +| **PRECACHE_TABLES_COUNT** | Specifies the minimum number of tables that should be specified for conversion in order to use "precache" technology. \\ Default value - "101". | 
 +| **REPLACE_RESERVED_WORDS** | This option replaces reserved words with the pattern provided in the option. | 
 +| **STARTROW** | This option defines the number of the first row that will be extracted from a table. \\ Default value - 1. | 
 +| **ROWSCOUNT** | This option defines the number of rows that will be extracted from a table. If this option is not set or empty, all the rows will be extracted. \\ Default value - Empty. | 
 +| **RPT** | This option defines the name of the folder where all the report files will be placed. The folder will be generated in the export directory. \\ Default value - "reports". | 
 +| **LOG** | This option defines the name of the conversion log file. This is a log file that will be generated during the conversion. \\ Default value - "sqlways.log". | 
 +| **TRACE** | This option allows to run the conversion in "Trace mode". If this option is set to "Yes", commented source code of the object will be added to the sql files. Sqlways.trc file, which contains detailed information about the conversion process will be generated as well.  \\ Default value - "sqlways.log". | 
 +| **DIVIDE_DATA_FILE_INTO_PARTS** | This option allows to generate multiple text files that store data for one table. If this option is set to "Yes", multiple .txt files will be generated. The maximum size of each file is by default equal to 2GB.  \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
 +| **GENERATE_IMPORT_SCRIPTS** | If this option is set to Yes, SQLWays Wizard will generate all the files required for performing import into the target database. Such files are ctl, .ldi and .bat files. If this option is set to "No", such files will not be generated. This option can also be set on the "Choose a Target Database" page of the SQLWays Wizard tool. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". | 
 +| **EXPORT_DATA** | This option defines data export process. If this option is set to "Yes", SQLWays will extract the data from a source database. If it is set to "No", data export will be omitted. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". | 
 +| **GENERATE_DDL_SCRIPTS** | If this option is set to "Yes", SQLWays tool will generate ddl files with the converted table definitions. If it is set to "No", ddl files will not be generated and only data will be extracted from a source database. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". | 
 +| **READ_DDL_SCRIPTS** | If this option is set to "Yes", SQLWays tool will generate ddl files with the converted table definitions. If it is set to "No", ddl files will not be generated and only data will be extracted from source database. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". | 
 +| **REPLACE_NOT_ALLOWED_CHARS_FPOS** | In some databases identifier names could contain specific characters that may not be allowed in the target database. This option was created in order to replace such characters only from the first position. Character that will replace not allowed characters should be specified in this option. |
 | **REPLACE_NOT_ALLOWED_CHARS** | In some databases identifier names could have specific characters that may not be allowed in the target database. This option was created in order to replace such characters. Сharacter that will replace not allowed characters should be specified in this option. | | **REPLACE_NOT_ALLOWED_CHARS** | In some databases identifier names could have specific characters that may not be allowed in the target database. This option was created in order to replace such characters. Сharacter that will replace not allowed characters should be specified in this option. |
-| **USE_QUERY_FOR_EXPORT** | If this option is set to "Yes", then sql queries will be used to extract data from source database. Queries can be specified either in GUI or in the sql file. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No". | +| **USE_QUERY_FOR_EXPORT** | If this option is set to "Yes", sql queries will be used to extract data from source database. Queries can be specified either in GUI or in the sql file. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No". | 
-| **EXPORT_QUERY_FROM_FILE** | If this option is set to "Yes", then an sql filethat contains sql queries will be usedthese queries will be used to extract data from the source database. Path to file with sql queries should be provided in the "EXPORTQUERYFILE" option. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | +| **EXPORT_QUERY_FROM_FILE** | If this option is set to "Yes", an sql file that contains sql queries will be used and these queries will be used to extract data from source database. A path to the file with sql queries should be provided in the "EXPORTQUERYFILE" option. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "No" or Empty. | 
-| **EXPORTQUERYTEXT** | This option contains stored queriesthat will be used to extract data from the source database. Queries are separated using the "\\". | +| **EXPORTQUERYTEXT** | This option contains stored queries that will be used to extract data from source database. Queries are separated using the "\\". | 
-| **EXPORTQUERYFILE** | This option works only when "EXPORT_QUERY_FROM_FILE" option is set to "Yes". In this option we need to define a path to the sql file with the queriesthat will be used to extract data from the source database. | +| **EXPORTQUERYFILE** | This option works only when "EXPORT_QUERY_FROM_FILE" option is set to "Yes". In this option we need to define a path to the sql file with the queries that will be used to extract data from source database. | 
-| **EXPORTQUERYTARGETNAMES** | In this option target table names should be specified, they will be used in the CREATE TABLE statements, that will be built for each query defined in the "EXPORTQUERYTEXT" option. Table names should be separated using the "\\". | +| **EXPORTQUERYTARGETNAMES** | In this option target table names should be specified. They will be used in the CREATE TABLE statements, that will be built for each query defined in the "EXPORTQUERYTEXT" option. Table names should be separated using the "\\". | 
-| **EXPORTQUERYTARGETNAMESFILE** | This option works only if "EXPORT_QUERY_FROM_FILE" option is set to "Yes". This option should specify a path to the file, that will store target table names for tables that will be created in the target database. |+| **EXPORTQUERYTARGETNAMESFILE** | This option works only if the "EXPORT_QUERY_FROM_FILE" option is set to "Yes". This option should specify a path to the file, that will store target table names for tables that will be created in the target database. |
  
 **Example**: **Example**:
Line 24: Line 39:
 \\ \\
  
-If you have any questions on the supported options or some features that you may need during your migration project, please contact our technical team: **__[[[email protected]]]__**+If you have any questions about the supported options or features that you need for your migration project, please contact our technical team: **__[[[email protected]]]__**
  
  
sqlways/command-line/sqlways-ini/wizard_common-section.1539352498.txt.gz · Last modified: October 12, 2018, 01:54:58 PM by alexandr.kirpichny
 
© 1999-2019, Ispirer Systems Ltd.
All Rights Reserved.  Privacy Statement