SQL Server

QoreDB connects to Microsoft SQL Server through the Tiberius driver (a native Rust implementation of the TDS protocol). Both modern SQL Server (Linux and Windows) and Azure SQL Database are supported.

Quick connect

Open New Connection, choose SQL Server, and fill the form. Unlike the SQL/Mongo drivers, SQL Server doesn't have a single canonical DSN scheme; you'll typically fill the fields directly.

Connection fields

Authentication modes

QoreDB supports three authentication modes:

SQL authentication (default)

Standard username and password against a SQL login defined inside SQL Server. Works on every platform (macOS, Windows, Linux). This is what most cloud providers (Azure SQL Database, RDS for SQL Server) require.

User: app_user
Password: ••••••••

Windows NTLM

Authenticate using a Windows account, even from a non-Windows machine. The username can be in either form:

DOMAIN\username
username@domain.example.com

Use NTLM when your SQL Server only accepts Windows credentials and you're connecting from outside a Windows session (for example, from a Mac or Linux box on a corporate network).

Windows Integrated (SSPI)

Use the credentials of the currently logged-in Windows user. Windows only. No username or password is needed; the OS handles the handshake transparently. This is the friendliest mode in a domain-joined enterprise environment.

SSL / encryption

SQL Server's encryption is binary in QoreDB:

• SSL off: encryption is disabled.
• SSL on: encryption is required. Server certificate is trusted automatically.

For production traffic over the public internet, leave SSL on. Most cloud-managed SQL Server deployments enforce encryption server-side and reject unencrypted connections.

Connection pool

Each saved SQL Server connection backs a pool of up to 10 underlying TDS connections, with a 15-second timeout when acquiring one. This lets you run several queries in parallel from the same QoreDB session without reconnecting.

Schema browsing

Once connected, expand the connection in the sidebar:

Connection → Database → Schema → Tables / Views / Routines

SQL Server has both databases (top-level containers) and schemas (namespaces inside a database). The default schema for a user is usually dbo. Tables in other schemas show up under their respective nodes.

Common issues

Where to go next

• SSH tunneling for SQL Server instances behind a bastion
• Vault and profiles to organize connections per environment
• Querying: editor and autocomplete for the SQL editor