SQL Loader Configuration(4.1)
- Jenni Wallin
The SQL Loader tab contains configurations related to the SQL query used for populating the database with data from external files, as well as error handling.
Setting | Description |
|---|---|
Database | Profile name of the database that the agent will connect to and forward data to. PostreSQL, SAP HANA, and SybaseIQ profiles are supported. |
SQL Statement | In this field you enter the SQL statement to be used for stating where the files containing the data are located, into which table in the database the data should be inserted, as well as the formatting of the data. See SQL Statements for SQL Loader(4.1) for information about how to write the statements. |
Abort if exception | Select this check box if you want the workflow to abort in case of an exception. |
Transaction Behavior
Emits
The agent does not emit any commands.
Retrieves
Cancel Batch If a cancelBatch is emitted by any agent in the workflow, all data in the current transaction will be disregarded. No closing conditions will be applied.
Input/Output Data
The agent receives UDRs of FileReferenceUDR type and emits UDRs of SQLLoaderResultUDR type. For more information regarding these 2 UDR types, you can refer to SQL Loader UDR Types(4.1).
MIM
The agent does not publish or access any MIM values. For information about the  Usage Engine MIM and a list of the general MIM parameters, see Administration and Management(4.1) .
Debug Events
Debug messages are dispatched when debug is used. During execution, the messages are shown in the Workflow Monitor and can also be stated according to the configuration done in the Event Notification Editor.
The agent does not itself produce any debug events. However, APL offers the possibility of producing events.