Specify how you want to execute the project in the Advanced tab.
Extract and Load
Extract Only
Load Only
Select Use client side load to enable bulk loading of data into the IQ database from files located on client machines.
Select Automatic load ordering to determine the load order at runtime by examining the destination table dependencies.
In the Archive path field, specify the location where you want to archive the temporary data files after the data has been successfully extracted from the datasource.
In the Derived load ID column field, specify the name of the destination table column into which the execution Load ID is to be loaded.
In the Extracted data directory field, enter a temporary storage location for data extracted to files. Data is loaded into IQ from this temporary directory. If you do not specify a location (default), data is stored in the Sybase IQ InfoPrimer temporary directory on the execution machine.
Specify the format of the temporary files used to store data extracted from a source (usually a source database), and before it is loaded into Sybase IQ from the Stage file format list. These files are created during the extract phase of the EL project execution.
The loader internally stages the data into temporary files before sending the data to Sybase IQ using the LOAD TABLE command. You can initially populate a fresh and empty Sybase IQ database using these stage files.
The IQ binary data format can be read faster by Sybase IQ, but takes longer to be written by Sybase IQ InfoPrimer, while the delimited text format is a bit slower when read by Sybase IQ, but faster for Sybase IQ InfoPrimer to generate. Sybase recommends using the delimited text format for better performance. However, when extraction and loading is done in two phases, select the IQ binary data format since loading into Sybase IQ is faster and the slower generation of the stage files do not affect the loading phase.
Select the Transaction type, which can be one of:
Select Single Transaction to load each table as a single transaction. If selected, the transaction is rolled back in case of an error during the load of the table.
Select Auto Commit to directly write each block of data read from the source to target and then commit it.
Select Periodic Commit, which is similar to autocommit, to load data with a periodic commit interval, defined by the commit threshold.
Select Restartable, which is similar to periodic commit, to allow restarting of the project from a point of failure.
Select Commit threshold to specify the number of records after which you want to commit data. This option is enabled only for the Periodic Commit and Restartable transaction types.
Specify the number of records to be extracted at one time in the Read block size field. This property is not available for the Load Only execution mode.
Select Continue on error to continue processing even if an error occurs when loading data into a database.
Specify the number of records to be extracted and loaded from each of the source into the target database, in the Row Limit field. For example, if the source table has 10000 rows, and you just want the first 1000 rows to be loaded into the target database, you can enter 1000 in this field. The row limit is not used if set to zero (default).
Select the Pass-through optimizations option to enable the tool to load data in the fastest possible way. Unselect this option if you want to prevent errors that may have been caused if you have selected this option and the tool has to make checks to see if the source is compatible with Sybase IQ. By default, the Pass-through optimizations option is selected and is disabled for EL Projects where the Source is set to IQ Binary formatted files.
Click Property options to set the EL project properties.