IQ Loader File via Load Table properties list

Interface

Specify the method or driver with which to connect to the target IQ database. The supported interfaces are Sybase and ODBC.

Host Name

Specify the host where the Sybase IQ target is running.

User and Password

Identify an authorized database user, and protect the database against unauthorized access.

Destination

Select the destination table from a set of existing tables.

Key

Select target key attributes to identify the records on Upsert or Delete operations.If no key is selected, the interface works with the primary key information, which is delivered from the DB host. An error is displayed if no primary key information is available.

Function

Select one of these load functions:

• Insert – to load records directly from the file into the selected target table.

• Upsert – to update the existing records and insert the new records. When you select Upsert, the existing records are replaced and not updated on an attribute level. You can use the Key property to specify the target attributes to identify the records you want to update.

If you have selected the Truncate option, all records are removed from the target table before loading. The Insert and Upsert function loads all records to the target table directly.

Use Binary Load File

Select to load data from an IQ binary load file.

Text Source

Identify the text file you want to use as the data source. From the Properties window, click the Text Source icon, select the file, and specify the format. See “Working with the Text Source property window”.

Use IQ Client Side Load

Bulk load data from files located on remote host machines into a target IQ database, using the LOAD TABLE statement.

Row Delimiter

Specify how each row is delimited:

• LF (line feed)

• CR (carriage return)

• CRLF (carriage return followed by a line feed)

Alternatively, you can enter a different delimiter.

Column Delimiter

Specify how columns are delimited:

• Tab

• Comma

• Semicolon

• Pipe

Alternatively, you can enter a different delimiter.

Load Script

The LOAD TABLE statement is generated at runtime based on the component settings, if this property is empty.

To use a customized script, right-click the component and select Generate Load Script. The LOAD TABLE script is generated for Insert. After you generate the script, you can click Load Script and edit the script.

Truncate

Remove all records from the destination table before the load.

Pre Processing SQL

Create a script that runs during component initialization.

Scripts can include one or more SQL statements. If you use multiple statements, separate them with a semicolon (;).

Post Processing SQL

Create a script that runs after all components execute.

Scripts can include one or more SQL statements. If you use multiple statements, separate them with a semicolon (;).

Database

Specify the database to use as data target. The database is used together with the specified user name, password, and host name.

Schema

Specify an owner to filter the table catalog.

Database Options

Set options that override performance defaults and control the behavior of some transactions.

See “Database connection settings”.

Null Indicator

Specify the string that represents null values in the source file.

Skip Rows

Specify the number of rows to skip at the beginning of the input file for a load. The default is 0.

Parallel format

Allow the LOAD TABLE command to run in parallel. To use this option, all columns, including the last, must be delimited by a single ASCII character.

Strip

Strip trailing blanks from values before they are inserted. This applies only to variable-length nonbinary data.

Byte Order

Specify the byte ordering during reads. This option applies to all binary input fields. If none are defined, this option is ignored. Sybase ETL always reads binary data in the format native to the machine it is running on (default is NATIVE). You can also specify:

• HIGH when multibyte quantities have the high- order byte first.

• LOW when multibyte quantities have the low- order byte first.

Block Size

Specify the default size, in bytes, in which input should be read.

Limit

Specify the maximum number of rows you want to insert into the table. The default is 0 for no limit.

ON File Error

Specify the action Sybase IQ should take when an input file cannot be opened, either because it does not exist or because you have incorrect permissions to read the file. For all other reasons or errors, it aborts the entire insertion. You can specify one of the following options:

• ROLLBACK (the default) – aborts the entire transaction.

• FINISH – finishes the insertions already completed and ends the load operation.

• CONTINUE – returns an error but only skips the file to continue the load operation. You cannot use this option with partial-width inserts.

Word Skip

Allow the load to continue when it encounters data longer than the limit specified when the word index was created.

IQ Lock Table in Exclusive Mode

Lock the target table to prevent it from being updated by concurrent transactions. When an exclusive table lock is applied, no other transaction can execute queries or perform any updates against the locked table. The IQ Lock Table in Exclusive Mode option also queues multiple projects that load the same table in Sybase IQ.

Wait Time for IQ Lock Table

Specify the maximum blocking time that the project should wait before acquiring an Exclusive lock.

Specify the time argument in the format hh:nn:ss.sss. If you do not enter a time argument, the server waits indefinitely until an Exclusive lock is available or an interruption occurs. When you specify “00:00:00.000” as the time argument, an Exclusive lock is acquired as soon as the project starts.

Use IQ Multiplex

Support multiplex execution by using multiple writers to load data into the IQ database.

Transactional

All work performed by the IQ Loader File via Load Table component, including pre-SQL and post-SQL, is done in a single database transaction that is committed when the project finishes normally. Select this option to roll back the transaction, if this component encounters an error. See “Job components” and “Enabling transactionality for projects and jobs” for information on the “Propagate Rollback” property.