Sybase ETL 4.8 lets you bulk-load data from text files located on remote host machines into Sybase IQ 15.0, using the “DB Bulk Load - Sybase IQ” and “IQ Loader File via Load Table” components.
In earlier versions of Sybase ETL, text files were required to be available on the same host machine as the IQ server. Also, Sybase ETL was required to be installed on the same machine as Sybase IQ. In version 4.8, you no longer need to install Sybase ETL and Sybase IQ on the same machine; the ETL server and Sybase IQ can communicate in a networked environment that allows you to bulk-load from a remote machine in a single step.
To enable client-side loading on Sybase IQ, set the allow_read_client_file and allow_write_client_file options
to On
.
You must set these options once on every IQ server.
Use Sybase Central to change the value of these two options:
Connect to the Sybase IQ 15.0 server.
Right-click and select Options to see a list of all the available permanent option settings for Sybase IQ.
Select allow_read_client_file and allow_write_client_file and
change the value to On
. The
default value is Off
.
Next, you need to set the server option property allow_read_client_file to On
.
To do this, run the following commands using isql or dbisql utility:
set option allow_read_client_file=on
GRANT READCLIENTFILE TO <group | user>
In ETL 4.8 client-side bulk loading is supported by
ODBC clients using the IQ 15.0 ODBC driver, which uses the Command
Sequence communication protocol (CmdSeq). The
protocol can use the read_client_file and write_client_file secure
SQL components to control how a client file is read or written to
a database. Use the -sf server option to enable
or disable features for a database server. For details, see the SQL
Anywhere 11.0 documention on Product Manuals Web site.
You can use “DB Bulk Load - Sybase IQ” and “IQ Loader File via Load Table” components to load text files to Sybase IQ located on a remote machine, when the text file:
Is generated using ETL but not written to the IQ host machine.
Is generated outside ETL and not placed on the IQ host machine.
In both scenarios, the text file must be in a format that is compatible with the loader components, which are mainly ASCII or binary data.
For more details on formats supported in Load Table statements, see “LOAD TABLE statement” in Chapter 6, “SQL Statements” of the Sybase IQ 12.7 Reference Manual.
For more details about component descriptions, see “DB Bulk Load - Sybase IQ,” in “Destination components,” and “IQ Loader File via Load Table,” in “Loader components,” in Chapter 5, “Components” in the Sybase ETL 4.8 Users Guide.