Overview

The SQL Executor node is used to define and execute SQL scripts or stored procedures against a selected data source in a Weave Workflow. It operates directly on the data source rather than on an upstream data stream, and the effect of each executed query is reflected in that data source.

Configuration is two parts: select a data source, then define one or more queries in the SQL Executor popup. Each query specifies a Title, a Type (SQL or Stored Procedure), and the Query text. The Result Tab reports execution metadata for each query rather than queried rows.

Note: “Workflow” is the in-UI term for what some Weave documentation calls a pipeline. This reference uses “Workflow.”

When to use it

  • Running SQL scripts directly against a data source as part of a Workflow.
  • Executing a stored procedure by name on a selected data source.
  • Applying data-source-side changes (inserts, updates) that should take effect in the source itself.
  • Running multiple queries in sequence from a single node.

Configuration components

ComponentDescription
Data SourceChoose the data source the queries run against.
Query ExecutorOpens the SQL Executor popup where queries are defined.
TitleProvide a name for the SQL query or stored procedure.
TypeChoose the query type: SQL or Stored Procedure.
QueryProvide the query to be executed or the name of the stored procedure.
Add (+)Adds another query to the node.

Result fields

The Result Tab reports execution details per query rather than the data returned:

FieldDescription
query_nameThe name of the executed query.
StatusThe execution outcome (e.g. SUCCESS).
StartThe execution start time.
EndThe execution end time.
DurationThe elapsed execution time.

Key behaviors

Executes against the data source. The node runs its queries directly on the selected data source, and the effect of each query is reflected in that data source rather than only in the Workflow.

Source-driven, not stream-driven. Unlike transformation nodes that act on an upstream data stream, SQL Executor is configured around a data source it queries.

Multiple queries per node. Several queries can be added with the add (+) action and applied together.

Status-only result. The Result Tab returns execution metadata (query name, status, timing), not the rows a SELECT would return.