Execute Query (Deprecated)
Use Execute Query for new workflows. Use Execute Query for result rows and Execute Non-Query for affected-row counts from data changes. The current query activity returns an IbDataTable rather than an unspecified Output.
Keep the existing node when maintaining a legacy workflow until its mappings and downstream bindings have been migrated and tested. The current activity is a replacement, not a drop-in change to the old output schema.
Description
The Execute Query activity runs a raw SQL statement against a connected database. It enables advanced operations and custom queries beyond standard insert, update, select, and delete.
Common settings
Use Process Data to bind supported inputs to workflow values or upstream outputs. See Common Activity Features for shared execution, error-handling, and output-persistence settings. Availability depends on the activity.
Design-Time Configuration
The following properties define how the activity connects to the database and executes the SQL query.
Connection Type
Specifies the database engine (for example, SQL Server, Oracle, MySQL, PostgreSQL). Selecting the correct type ensures compatibility with the target database.
Connection Name
Select a preconfigured database connection that defines the server, credentials, and security settings.
Query
Specifies the SQL statement to be executed. The Query must be valid for the selected database type and may return a result set or perform data modification operations.
Timeout
Specifies the maximum time (in seconds) that the activity will wait for the Query to complete. The default value is 600 seconds.
Outputs
Output
Returns the result produced by the SQL query.
For queries that return data (for example, SELECT), this output contains the result set.
For data-modifying queries (for example, INSERT, UPDATE, DELETE), it may return the number of affected rows or the execution status.
Execution settings
Configure Wait All Incoming when execution paths converge, and On Error for failure handling. Select Inherit where available to use the workflow-level error policy.