Differences

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

Link to this comparison view

Next revision Both sides next revision
guides:migration-toolkit:command-line:sqlways-ini:mysql-section [2019/06/11 00:26]
127.0.0.1 external edit
guides:migration-toolkit:command-line:sqlways-ini:mysql-section [2019/10/18 11:26]
darya.prikhodkina
Line 11: Line 11:
 | **PWD** | Specifies the user password which is used in generated scripts for MySQL. | | **PWD** | Specifies the user password which is used in generated scripts for MySQL. |
 | **TABLE_TYPE** | This option specifies the table type which is used when creating tables in MySQL database. MySQL supports two 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, the tool generates TYPE=InnoDB clause in CREATE TABLE statements for MySQL. | | **TABLE_TYPE** | This option specifies the table type which is used when creating tables in MySQL database. MySQL supports two 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, the tool generates TYPE=InnoDB clause in CREATE TABLE statements for MySQL. |
-| **IMPORT_FROM_CLIENT** | If Yes is specified, the LOCAL keyword is generated for MySQL LOAD DATA INFILE command which is used to import data to MySQL. When LOCAL is specified, data files can be located on the client host. \\ If No is specified, the LOCAL keyword is not generated and data files must be located on the server before import. \\ Possible values - Yes, No. The default value is Yes. | +| **IMPORT_FROM_CLIENT** | If "Yes" ​is specified, the LOCAL keyword is generated for MySQL LOAD DATA INFILE command which is used to import data to MySQL. When LOCAL is specified, data files can be located on the client host. \\ If "No" ​is specified, the LOCAL keyword is not generated and data files must be located on the server before import. \\ Possible values - \"Yes""No". The default value is "Yes". | 
-| **DATA_LOAD_OPTION** | If Replace is specified, existing rows will be 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 will not be updated when primary or unique key values are equivalent to the values that exist 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 will be 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 will not be updated when primary or unique key values are equivalent to the values that exist in the table. The rows from the text file which do not match primary or unique key in the table are inserted. | 
-| **ENABLE_PARTITIONING** | This option controls partitioned tables conversion for Oracle to MySQL and MSSQL to MySQL migration directions. If it is set to Yes, partitioning for tables conversion will be migrated to target MySQL database. Otherwise partitioning will be omitted. Possible values are Yes, No. The default value is No. | +| **ENABLE_PARTITIONING** | This option controls partitioned tables conversion for Oracle to MySQL and MSSQL to MySQL migration directions. If it is set to "Yes", partitioning for tables conversion will be migrated to target MySQL database. Otherwise partitioning will be omitted. Possible values are "Yes""No". The default value is "No". | 
-| **EXISTS2JOIN** | If it is set to Yes, all the occurrences of EXISTS clauses in SELECT statements will be replaced by the tables placed to common FROM clause and conditions placed to common WHERE clause. Possible values - Yes, No. The default value is No. | +| **EXISTS2JOIN** | If it is set to "Yes", all the occurrences of EXISTS clauses in SELECT statements will be replaced by the tables placed to common FROM clause and conditions placed to common WHERE clause. Possible values - "Yes""No". The default value is "No". | 
-| **IN2JOIN** | If this option is set to Yes, all the occurrences of IN clauses in WHERE condition will be moved to JOIN conditions with ON clause. Possible values - Yes, No. The default value is No. | +| **IN2JOIN** | If this option is set to "Yes", all the occurrences of IN clauses in WHERE condition will be moved to JOIN conditions with ON clause. Possible values - "Yes""No". The default value is "No". | 
-| **FOREIGN_KEY_CHECKS** | This option was added to ignore foreign key constraints during LOAD DATA operation and to ignore check of data when adding FOREIGN KEY constraints to the table. Possible values - Yes, No. The default value is No. |+| **FOREIGN_KEY_CHECKS** | This option was added to ignore foreign key constraints during LOAD DATA operation and to ignore check of data when adding FOREIGN KEY constraints to the table. Possible values - "Yes""No". The default value is "No". |
 | **CONVERT_PARTITIONS** | This option allows to convert RANGE and LIST partitions for Oracle to MySQL conversion direction. \\ Possible values - "​Yes",​ "​No"​ or empty. Default value - "​No"​ or empty. | | **CONVERT_PARTITIONS** | This option allows to convert RANGE and LIST partitions for Oracle to MySQL conversion direction. \\ Possible values - "​Yes",​ "​No"​ or empty. Default value - "​No"​ or empty. |
 | **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 the maximum value of VARCHAR2 is equal to 32767, and in MySQL with utf8 it is 21 844. Thus 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 the maximum value of VARCHAR2 is equal to 32767, and in MySQL with utf8 it is 21 844. Thus 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. |