Differences

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

--- guides:migration-toolkit:command-line:sqlways-ini:mariadb-section [2019/06/11 00:26]
127.0.0.1 external edit
+++ guides:migration-toolkit:command-line:sqlways-ini:mariadb-section [2019/10/18 11:13]
darya.prikhodkina
@@ Line 4: / Line 4: @@
 ^  Option name  ^ Description  ^
 | **BIN** | Specifies the directory where MySQL.exe utility is located. |
-| **HOST** | Specifies a remote host name where a target MariaDB database is located. |
+| **HOST** | Specifies a remote host name where target MariaDB database is located. |
 | **DATABASE** | Specifies the database name which is used in generated scripts for MariaDB. |
 | **PORT** | This option sets port number that will be used to connect to MariaDB database.   |
-| **TARGET_VERSION** | Specifies the target version of the MariaDB database. If this option is empty the latest MariaDB database version will be used. \\ Note: According to the version number conversion results may differ. |
+| **TARGET_VERSION** | Specifies target version of MariaDB database. If this option is empty the latest MariaDB database version will be used. \\ Note: According to the version number conversion results may differ. |
 | **USER** | Specifies the user name which is used in generated scripts for MariaDB. |
 | **PWD** | Specifies the user password which is used in generated scripts for MariaDB. |
 | **TABLE_TYPE** | This option specifies the table type which is used when creating tables in MariaDB database. MariaDB supports two different kinds of tables: transaction-safe tables (InnoDB and BDB) and not transaction-safe tables (HEAP, ISAM, MERGE, and MyISAM). \\ For example, when table_type=InnoDB is selected, SQLWays generates TYPE=InnoDB clause in CREATE TABLE statements for MariaDB. |
-| **DATA_LOAD_OPTION** | If Replace is specified, existing rows are updated in an existing table based on primary or unique key information or added to the table if a primary key is not matched. If Ignore is specified, existing rows in the table are not updated, when primary or unique key values are equivalent to existing values in the table. The rows from the text file which do not match primary or unique key in the table are inserted. |
+| **DATA_LOAD_OPTION** | If "Replace" is specified, existing rows are updated in an existing table based on primary or unique key information or added to the table if a primary key doesn't match. If "Ignore" is specified, existing rows in the table are not updated, when primary or unique key values are equivalent to existing values in the table. The rows from the text file which do not match primary or unique key in the table are inserted. |
-| **CHARACTER_SET** | This option defines the encoding that will be used to store the extracted data in the files in export folder. \\ Also according to the assigned value, this option may change the conversion of VARCHAR data type into TEXT data type. For example, when migrating from Oracle database to MySQL with utf8 encoding, maximum varchar length is different. In Oracle maximum value of VARCHAR2 is equal to 32767, and in MySQL with utf8 it is - 21 844. So if this option is set to "UTF8", all the VARCHAR2 data types, with length greater than 21 844, will be converted into TEXT in MySQL. |
+| **CHARACTER_SET** | This option defines the encoding that will be used to store the extracted data in the files in export folder. \\ Also according to the assigned value, this option may change the conversion of VARCHAR data type into TEXT data type. For example, when migrating from Oracle database to MySQL with utf8 encoding, maximum varchar length is different. In Oracle maximum value of VARCHAR2 is equal to 32767, and in MySQL with utf8 it is 21 844. So if this option is set to "UTF8", all VARCHAR2 data types with length greater than 21 844 will be converted into TEXT in MySQL. |
-| **IMPORT_FROM_CLIENT** | If Yes is specified, the LOCAL keyword is generated for MariaDB LOAD DATA INFILE command which is used to import data to MariaDB. When LOCAL is specified, data files can be located on the client host. \\ If No is specified, the LOCAL keyword is not generated, thus the data files must be located on the server before importing. \\ Possible values - Yes, No. The default value is Yes. |
+| **IMPORT_FROM_CLIENT** | If "Yes" is specified, the LOCAL keyword is generated for MariaDB LOAD DATA INFILE command which is used to import data to MariaDB. When "LOCAL" is specified, data files can be located on the client host. \\ If "No" is specified, the LOCAL keyword is not generated, thus the data files must be located on the server before importing. \\ Possible values - "Yes", "No". The default value is "Yes". |
-| **PRESERVE_COMMENTS** | This option controls whether the comments inside the sql should be saved during the import process. If this option is set to "Yes", SQLWays will generate command to mysql.exe utility with the option ”–comments”. And mysql.exe utility will save the comments inside the sql code during the import. If this option is set to "No", SQLWays will use ”–skip comments” option with mysql.exe utility. And this utility will not save comments inside the SQL code during the import.\\ Possible values - "Yes" or "No". \\ Default value - "No" or Empty. |
+| **PRESERVE_COMMENTS** | This option controls whether the comments inside the SQL should be saved during the import process. If this option is set to "Yes", SQLWays will generate command to mysql.exe utility with the option ”–comments”. And mysql.exe utility will save the comments inside the SQL code during the import. If this option is set to "No", SQLWays will use ”–skip comments” option with mysql.exe utility. And this utility will not save comments inside the SQL code during import.\\ Possible values - "Yes" or "No". \\ Default value - "No" or Empty. |
-| **CREATE_CONDITION_HANDLER** | This option was created to emulate the Transact-SQL behavior inside the MariaDB stored procedures and functions when the error in one of the statements inside the procedure or function body arises. By default this option is set to "Yes", which means that SQLWays adds the CONDITION HANDLER to each “BEGIN…END” block that handles the error arose without terminating the procedure or function execution. The errors are hidden in this case. When this option is set to "No", no CONDITION HANDLER is added and the first error encountered during the procedure or function run terminates the procedure or function execution. The error message is returned after the procedure terminates. \\ Possible values - "Yes" or "No". \\ Default value - "Yes". |
+| **CREATE_CONDITION_HANDLER** | This option was created to emulate the Transact-SQL behavior inside MariaDB stored procedures and functions when an error in one of the statements inside a procedure or function body arises. By default this option is set to "Yes", which means that SQLWays adds the CONDITION HANDLER to each “BEGIN…END” block that handles the error arose without terminating the procedure or function execution. The errors are hidden in this case. When this option is set to "No", no CONDITION HANDLER is added and the first error encountered during the procedure or function run terminates the procedure or function execution. The error message is returned after the procedure terminates. \\ Possible values - "Yes" or "No". \\ Default value - "Yes". |
-| **ENABLE_LOCAL_LOAD** | This option controls the local data load into MariaDB database. If this option is set to Yes, mysql.exe utility will be run with the local-infile option, which allows to use LOAD DATA LOCAL command in the .ldi file to load data into the target server from the local machine. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". |
+| **ENABLE_LOCAL_LOAD** | This option controls the local data load into MariaDB database. If this option is set to "Yes", mysql.exe utility will be run with the local-infile option, which allows to use LOAD DATA LOCAL command in the .ldi file to load data into the target server from the local machine. \\ Possible values - "Yes", "No" or Empty. \\ Default value - "Yes". |
 | **SSL_CA** | This option defines the path to a file in PEM format that contains a list of trusted SSL certificate authorities. \\ Default value - Empty. |
 | **SSL_MODE** | This option specifies the security state of the connection to the server. \\ Possible values - PREFERRED, DISABLED, REQUIRED, VERIFY_CA, VERIFY_IDENTITY and Empty. \\ Default value - Empty. |