SQL Server

SQL Server is Microsoft's network SQL engine. TableR connects with Windows or SQL Server authentication, auto-detected from the host. Point TableR at an existing server by filling the connection form, or let TableR start a local SQL Server for you with the built-in bootstrap when you do not have a server yet.

Overview

TableR speaks the native SQL Server protocol (TDS), so it works with a local install, a container, a managed service (Azure SQL Database, Amazon RDS for SQL Server, and similar), or a bootstrapped local server. The authentication mode — Windows or SQL Server — is detected from the host you enter.

• Local development — connect to localhost,1433, or bootstrap a local server.
• Named instances — use SERVER\INSTANCE, or set the instance name field.
• Remote / managed — use the provider endpoint and set Encrypt appropriately.

Before you start

• A reachable SQL Server (host and port), or use Local bootstrap instead.
• For SQL authentication: a login name and password.
• For Windows authentication: leave the username empty to use the current Windows account.
• Optionally, the specific database to open on connect.
• For remote servers: network access to the port and appropriate Encrypt settings.

Connection fields

These defaults match TableR's SQL Server connection form. Secrets are written to the operating system keyring, never to plain configuration files.

Connect with the form

1. 1
   Choose SQL Server

   Open the launcher and pick the SQL Server card.

2. 2
   Enter host and port

   Use localhost,1433 for a local server, SERVER\INSTANCE for a named instance, or your provider's endpoint for a remote one.

3. 3
   Pick an authentication mode

   Leave the username empty for Windows authentication, or enter a login and password for SQL Server authentication.

4. 4
   Pick a database (optional)

   Set a database to open it directly, or leave it blank to use the login's default.

5. 5
   Set encryption for remote

   Set Encrypt to Mandatory for remote servers; keep Trust server certificate on for local self-signed certificates.

6. 6
   Save and connect

   Save the profile so it reappears in the launcher, then connect.

Local bootstrap

If you do not have a server, TableR can start a local SQL Server for you — no separate install required.

1. 1
   Select SQL Server

   Pick SQL Server in the launcher.

2. 2
   Choose Local bootstrap

   TableR provisions and starts a local server on your machine.

3. 3
   Start querying

   A connection is created for you; open a SQL tab and run a query.

SSL/TLS

SQL Server controls encryption with the Encrypt setting rather than a URI parameter. Local servers usually need no encryption; for anything over a network, set Encrypt to Mandatory.

• Encrypt: Optional — encrypt only if the server negotiates it (typical for local development).
• Encrypt: Mandatory — always encrypt the connection (use for remote and managed servers).
• Trust server certificate — on by default for local self-signed certificates; turn it off to validate the server's certificate chain.

Verify the connection

Once connected, open a SQL tab and run a quick check:

SELECT @@VERSION;
SELECT DB_NAME(), SYSTEM_USER;

If both statements return rows, the connection and credentials are working.

Troubleshooting

Next steps