SQL Server — rdSQL Docs

rdSQL speaks the TDS protocol directly through a native driver — there is no ODBC driver to install and no JDBC bridge to configure.

Connect#

Click New Connection.
Set a Connection Name and choose SQL Server as the Database Engine.
Fill in Host, Port (default 1433), Database (optional), Username, Password — SQL Server authentication; Windows/Active Directory authentication isn't supported yet.
Set SSL Mode:
- require — connect with TLS and trust the server's certificate. This is the common case for local and dev SQL Server with its default self-signed certificate (the equivalent of TrustServerCertificate in other clients).
- disable — turn encryption off entirely.
Click Test, then Save.

What you get#

Like the MySQL family, one connection sees every database on the server. System databases (master, tempdb, model, msdb) are hidden by default — enable Show system schemas in the connection's Security tab to reveal them alongside sys and INFORMATION_SCHEMA. Tables in non-dbo schemas appear as schema.table in the tree.

SET, USE and #temp tables carry over between statements on the same connection — in the editor too, the way SQL Server Management Studio behaves.

Known limitations#

Compare & Sync, the Health Monitor, Users & Privileges, Migration Studio, and the Views/Triggers/Procedures/Events object editor don't support SQL Server yet. Core browsing, querying, table and database DDL, and backup & restore are fully supported.

Troubleshooting#

Login failed for user — confirm SQL Server authentication is enabled on the server (not Windows-auth-only) and the login has a database mapped.
Connection timed out — check the server listens on the TCP port you configured (1433 by default) and isn't blocked by a firewall. rdSQL does not use SQL Browser (UDP 1434) for dynamic ports — set the explicit port.
Certificate / TLS errors — set SSL Mode to require, which trusts the server's certificate automatically.