Skip to main content

Execute Non Query

Executes non-query SQL statements (UPDATE, DELETE, INSERT) on an Oracle database.

Common Properties

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs

  • Connection Id - The ID of the database connection to use.
  • Transaction Id - The ID of the transaction to use (optional).
  • SQL Query - The SQL non-query statement to execute, with optional template variables.

How It Works

The Execute Non Query node runs SQL statements that don't return data by:

  1. Validating the provided Connection Id
  2. Looking up the connection and transaction in the shared dictionaries
  3. Using a template engine to render the SQL query with context data
  4. Creating an OracleCommand with the rendered SQL
  5. Executing the command using ExecuteNonQuery()

Requirements

  • An active database connection established with the Connect node
  • Valid SQL non-query statement (UPDATE, DELETE, INSERT)
  • Appropriate permissions to execute the SQL statement
  • Valid connection and transaction IDs when provided

Error Handling

The node will return specific errors in the following cases:

  • Empty or invalid Connection Id
  • Connection ID not found in the connections dictionary
  • Transaction ID not found in the transactions dictionary (when provided)

Usage Notes

  • The SQL Query can include template variables using double curly braces (e.g., {{variable}})
  • Template variables are populated from the message context
  • Non-query statements include UPDATE, DELETE, INSERT, and DDL statements
  • When using a Transaction Id, the statement will be part of that transaction
  • The node does not return any data, only executes the statement
  • For SELECT statements, use the Execute Query node instead