This option is used to generate the sqlways.trc file in the export directory containing more detailed information regarding the export process. This information is primarily used by SQLWays developers to fix the export issues that may arise.

NOTE: If this option is checked each SQL with the objects creation statements contains the commented source SQL code of the object in the same file.

By default the Divide data file into parts of check-box is is not checked, so the text file with exported table is not divided into parts. In this case the sqlways.log file contains the record like:

Output data file: C:\Program Files\Ispirer\SQLWays 3.7\Project\gsd_locker_assignment.txt

If the Divide data file into parts of check-box is checked it is possible to define the largest possible file size for text files in the edit box (2G is specified by default). G, M, K postfixes can be specified to define Gigabytes, Megabytes and Kilobytes. When the file size value specified is exceeded SQLWays divides the text file into parts. All parts are named the same except for the number at the end of the name, like:

table_name.txt
table_name2.txt
… 
table_nameN.txt

Note: The minimal part size must exceed the maximum row size (without LOB data).

In case when splitting is specified the sqlways.log file contains:

Data file was divided into 2 files of 1G:
 Output data file: C:\Program Files\Ispirer\SQLWays 3.7\Project\gsd_locker_assignment.txt
 Output data file: C:\Program Files\Ispirer\SQLWays 3.7\Project\gsd_locker_assignment2.txt

Using this text-box you can specify the path to the location of the files, that will contain the LOB data for load into the Oracle or IBM DB2 databases after the export.

In the LOB directory box, enter the path or click (…) to indicate the target folder for the LOB data objects (large objects such as CLOB and BLOB data types in Oracle, IBM DB2; TEXT and IMAGE data types in Microsoft SQL Server, Sybase; MEMO data types in Access and FoxPro). For each LOB value, SQLWays creates one file in the LOB directory, specifying the file name in the ASCII file containing the table rows.

The default value is the lob sub-directory of the export directory.

This option controls the LOB data storage in the output file(s). If this option is specified the data of the LOB columns (CLOB, BLOB, TEXT, IMAGE and MEMO) is written inside the text file.

This option influences the LOB values storage when the target databases are Oracle and IBM DB2. As the default for these databases each LOB value is written into a separate file. This eliminates the risk of misinterpreting the data during the load into Oracle using SQL Loader and IBM DB2 using IMPORT/LOAD utilities.

This option doesn't influence the LOB data storage for the target databases, like: Microsoft SQL Server, Sybase, MySQL or Pervasive.SQL. For these databases the LOB data is always written inside the text file, as data load utilities and commands like BCP for Microsoft SQL Server and Sybase, LOAD DATA INFILE command for MySQL and BUTIL utility for Pervasive.SQL don't have the option to load the data into one of the columns in the table from a separate file.

Ispirer Home Page Ispirer SQLWays Migration Product Page Request SQLWays