SQL Server
Collection SQL_SERVER and Delivery SQL_SERVER_EXEC. It is the only one of the four dialects
that accepts calling a procedure by name in the command fields (EXEC my_procedure :payload, :datetime) and running the Transformer output as SQL with EXEC (:transformer) — see
procedures and dynamic SQL.
Connection
| Field | What it does |
|---|---|
| Host / Port | SQL Server host and port. Default 1433 |
| Database | Database opened by the connection — every query and command runs against it |
| Instance Name | Named instance (e.g. SQLEXPRESS). Blank = default instance |
| User / Password | SQL authentication. Windows integrated authentication is not used |
| Encrypt | On by default: negotiates TLS with the server. Turn it off only for an old server that does not accept encryption |
| Trust Server Certificate | Accepts the server certificate without validating the chain — required with a self-signed certificate, common on shop-floor SQL Servers |
| Test Query (Keep Alive) | Query used by the Test Connection button and by every Keep Alive cycle. Blank = SELECT 1 |
Vocabulary blocked in this dialect
On top of the DDL/DCL barred in every dialect, this one blocks:
OPENROWSET, OPENQUERY, OPENDATASOURCE, SHUTDOWN, DBCC, procedures sp_/xp_, EXECUTE AS
The full check — leading verb, chained statements and the neutralisation of comments and literals — is described in what CMS blocks in SQL fields.
The behaviour shared by all four databases — result modes, marking what has been read and placeholders — is described in Databases.