connector
SQL Server
Microsoft SQL Server, on-prem or managed.
Connection fields
| Field | Required | Description |
|---|---|---|
server | Yes | Hostname or IP address of the SQL Server instance. |
port | No | Defaults to 1433. |
user | Yes | SQL Server login. |
password | No | Password for the login. |
db | Yes | Database name to connect to. |
encrypt | No | One of "off", "optional", or "required" (default). Controls whether the connection is TLS-encrypted. |
trust_server_certificate | No | When true, skips validating the server's TLS certificate. Defaults to false. |
Example configuration
{
"server": "sql.internal.example.com",
"port": 1433,
"user": "arcodash_reader",
"password": "••••••••",
"db": "analytics",
"encrypt": "required",
"trust_server_certificate": false
}Caveats
- Auto-LIMIT isn't supported for this connector — T-SQL uses TOP/OFFSET-FETCH rather than LIMIT, so an unbounded SELECT runs unmodified.
- binary, xml, udt, and sql_variant columns aren't decoded and will error the whole query if selected — exclude them or cast to a supported type.
- There's no connector-level query timeout for SQL Server — only the worker's overall run timeout applies, since the underlying driver (tiberius) has no query-level timeout of its own.