SQLines Data is a scalable, high performance data transfer, schema conversion and validation tool.
You can run the tool from a command line, and this article describes the configuration file options. Additionally, you can specify options in Command Line.
The default configuration file is sqldata.cfg located in the current directory. You can use -cfg command line option to specify another location and file name for the configuration file.
DDL (schema) migration options.
When -ddl_tables=yes the tool executes DDL statements defined by -topt command line option (CREATE; DROP and CREATE TABLE, or TRUNCATE TABLE statements). When no is specified the tool does not perform any DROP, CREATE, TRUNCATE statements for tables.
Default is yes.
When -constraints=yes the tool migrates table constrains (primary and unique keys, check constraints, foreign keys).
Default is yes. It is possible to set -ddl_tables=no and -constraints=yes to migrate constraints only for existing tables.
When -indexes=yes the tool migrates table indexes. Note that some indexes are defined by constraints (like primary or unique keys) and they will not be migrated by this option.
Default is yes. It is possible to set -ddl_tables=no and -indexes=yes to migrate indexes only for existing tables.
Data transfer options.
When SQLines Data transfers LOB values it uses LOB API functions to read and write LOB data in parts as the maximum size of a LOB column in the table is unknown. Using LOB API functions significantly reduces the transfer performance even if the actual data in LOB columns do not have large size (i.e. 10-30 KB).
When you set -fetch_lob_as_varchar=yes, SQLines Data still creates LOB columns in the target database, but transfers data as regular VARCHAR columns without using LOB API. This can increase performance by 3x - 10x.
Set this option only if you know that the data in LOB columns do not exceed 32,700 bytes, otherwise a data truncation error raises.
The default value is no that means LOB API is used to transfer LOB data.
Options applied when MySQL is the source or target database.
When a value is set for the -mysql_set_foreign_key_check option, each session executes the following statement after establishing the connection:
If -mysql_set_foreign_key_check=0 is set, each session executes SET FOREIGN_KEY_CHECKS=0 that
This can significantly increase the migration performance as MySQL requires significant time (often much more than data transfer time) to check foreign keys, but inconsistent data can be loaded into tables that can violate referential constraints.
Options applied when Informix is the source database.
Informix ODBC driver ignores CLIENT_LOCALE options set in SETNET32 and environment variables, so you have to set the -informix_client_locale option to specify which client locale to use for the connection to Informix.
If you do not set option, and the database locale and your default client locale is difference, you can get conversion errors:
|21005||[Informix][Informix ODBC Driver]Inexact character conversion during translation.|
-- CLIENT_LOCALE=en_US.819 will be set for the connection -informix_client_locale=en_US.819