esp_iqloader

Archives data from one or more Event Stream Processor streams into Sybase IQ.

The esp_iqloader command archives data from one or more Event Stream Processor streams into Sybase IQ, either in real-time mode or in batch mode.

esp_iqloader subscribes to the streams that require archiving, then writes the data to an intermediate file either in a delimited format suitable for bulk-loading for inserts, or as SQL DML statements for updates and deletes. esp_iqloader uses the LOAD TABLE statement feature of Sybase IQ to archive inserts, and archives updates and deletes via ODBC.

Note: When running esp_iqloader in data warehousing mode (-I argument), updates are treated as inserts, and deletes are ignored.

esp_iqloader closes if it encounters an error. If esp_iqloader, the Event Stream Processor, or Sybase IQ stop, on restart esp_iqloader begins archiving data from the last archived transaction. esp_iqloader tracks the most recent archived transaction.

Note: Ensure that every stream to be archived uses the Persistent Subscribe Pattern. Associate every stream with two additional streams. The first stream is a log stream, which contains the transaction logs for the stream to archive. The second stream is a control stream that is an input to the log stream, which serves as a gateway into the log stream to purge the archived transaction logs. Use the ESP Studio to create both the log and control streams that use the Persistent Subscribe Pattern.

The control stream and the log stream must be persisted to guarantee that no transaction is lost if the Event Stream Processor fails. To ensure that the data stream can regenerate itself, create at least one log store to store both the control stream and the log stream.

To stop a running esp_iqloader process, enter Ctrl+C on the command line.

Limitations and known issues:

Syntax

esp_iqloader -f configFile -p [<host>:]<port>/workspace-name/project-name

Required Arguments

Options