User and Password
|
Identify an authorized database user
and protect the database against unauthorized access.
|
Shared Connection
|
Allow the component
to share a single connection to the database with other target components
that have identical connection and database parameters.
A connection can be shared only between components within
the same project. Components in different projects within the same
job cannot share a connection.
Components that use the same database interface and login
information, but use different database options cannot share a
connection, and generate an error when the project is executed or
simulated.
Note: Connection sharing is not supported if the Use IQ Multiplex
property is enabled.
|
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 appears if no primary key information
is available.
|
Function
|
Select one of these load functions: Insert (default) – load records directly
into the selected target table using the specified file path or pipe
name.
Upsert – update existing records and insert
the new records. Existing records are replaced and not updated on
an attribute level. You can use the Key property to specify the
target attributes identifying the records you want to update.
Delete – delete records from the target
tables based on the keys in the incoming data. You can use the Key
property to specify the target attributes identifying the records
you want to delete.
If you have selected the Truncate option, all records are
removed from the target table before loading. In this scenario,
the selected functions perform as follows: Insert
and Upsert load all records to the target table directly.
Delete does not move any records, but
preprocessing and postprocessing SQL statements are still executed.
|
Truncate
|
Remove all records from the destination
table before the load.
|
Use IQ Client Side Load
|
Add records from files located on remote
host machines into the Sybase IQ table, using the LOAD TABLE statement.
|
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.
Note: If a custom load script is provided, the Function property
is ignored.
|
Load Stage (Server)
|
Specify the server path to the data file
or, leave it empty when using a pipe.
If the Sybase IQ server needs to use a different path to the
temporary data file than specified in the Load Stage property, enter
it here.
|
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 (;).
Note: If you have selected the Truncate option, all records
from the destination table are deleted before the preprocessing
SQL statement is executed.
|
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
|
Identify the database to use as datasource. If you select this option, you must also select an appropriate
interface, and in some cases, specify an appropriate user ID and
password.
|
Schema
|
Identify the schema or owner you want
to use as datasource. The objects that appear are restricted accordingly
and new tables are created in the schema you specify.
|
Standardize Data Format
|
Convert incoming DATE and NUMBER information into
a standard format that Sybase IQ InfoPrimer can move between systems that
support different formats.
Dates are converted into this format: YYYY-MM-DD
hh:mm:ss.s. For example: 2005-12-01 16:40:59.123
Numbers are converted using a period (“ .”)
as the decimal separator. |
Database Options
|
Set options that override performance
defaults and control the behavior of some transactions.
|
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:mm:ss.sss.. When you do
not enter a time argument, the server does not wait.
When you specify “00:00:00.000” as the time argument, the server waits indefinitely until an
exclusive lock is available or an interruption occurs.
|
Use IQ Multiplex
|
Support multiplex execution by using
multiple writers to load data into the IQ database.
|
Transactional
|
All work performed by the component, including preprocessing SQL statements and postprocessing SQL statements, 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.
|