Microsoft SQL Server (T-SQL)

Microsoft SQL Server connections speak T-SQL and use the go-mssqldb driver. Pro and above.

Auth

• SQL Server authentication (username + password)
• Windows / Active Directory authentication where the server allows it
• Azure SQL with an access token

Credentials resolve from the active Space’s vault on connect, same as every other engine.

Identifier quoting

T-SQL uses square brackets — [dbo].[Orders]. ShellYard auto-quotes mixed-case or reserved identifiers so SELECT * FROM Orders works whether the table is Orders, ORDERS, or [orders] on disk.

Schema browser

The browser walks database → schema → table / view / synonym → column. Right-click a table for a SELECT TOP 100 * skeleton; right-click a stored procedure for an EXEC skeleton with parameter placeholders.

Health

The Health tab surfaces sys.dm_exec_requests (active queries with wait type and blocking session), sys.dm_os_wait_stats (cumulative waits), sys.dm_db_index_usage_stats (index hits and seeks vs scans), and basic database-size growth from sys.master_files. See Health dashboards.

SSH-tunnel routing

SQL Server connections can be pinned to an active SSH session the same way the other engines route — the wire connection flows out of the jump host instead of your local network. See SSH-tunnel routing.

Tier behavior

• Free — not available. Free Data Inspector covers SQLite only.
• Pro and above — SQL Server connections sync via the same KMS-wrapped path as Postgres / MySQL / Redis / Mongo.