sql executor
Icon |
|
|---|---|
Use When |
Data needs written to or deleted from a database using a specific sql statement |
Samples |
|
Description |
The Sql Executor is used to write data to a SQL compliant relational database by specifying a sql query. The Sql Executor can take one or more input messages. The sql will be executed based on the 'Run When' option, either Per Message - one time per message received, Per Entity - for every entity record in an input message or On Success - one time at flow completion. |
Inbound Message Type |
Model Based Message |
Output Message Type |
Text Based Message |
Control Message Handling |
Input: As messages are received, the provided Sql (as defined by the settings below) will be processed. A status results text message will be forwarded. Output: A single control message will be forwarded to downstream components once all messages have been processed through this step. |
| Name | Description |
|---|---|
Resource |
The SQL Database Resource on which the SQL query should be run to write the data. |
Whether to forward failed messages and continue processing. This is the name of a linked component to forward the failed messages to. |
|
Run When |
Timing of when to run the defined sql. Whether the sql executes after each message received, once per entity record in a message or on flow completion. |
Get SQL From Message |
Whether to use SQL provided on an input message instead of provided by File or below Sql |
File |
File containing Sql statements to run. If a value is included here it will be used instead of any Sql Statements in the next box. |
Sql |
Sql statement(s) to run. Could be an insert, update or delete statement. Multiple statements can be executed by including a semi-colon (;) between sql statements. |