SQL Server

Connect a Microsoft SQL Server database (self-hosted, RDS, or Managed Instance) with a connection string.

Reads tables from any Microsoft SQL Server database. Flitch only issues SELECT queries, so it can never write to your database (use a read-only login to enforce this).

Add a source

SQL Server connects with a connection string (a SQL login over TLS).

Prerequisites

A reachable SQL Server host and database.
A login with read access to the tables you want.

-- In the master database:
CREATE LOGIN flitch_readonly WITH PASSWORD = 'choose-a-strong-password';
-- In your target database:
CREATE USER flitch_readonly FOR LOGIN flitch_readonly;
ALTER ROLE db_datareader ADD MEMBER flitch_readonly;

Build the connection string

Server=tcp:your-host,1433;Database=mydb;User Id=flitch_readonly;Password=password;Encrypt=true

For a self-signed certificate (common on self-hosted instances) add ;TrustServerCertificate=true. A JDBC string (jdbc:sqlserver://host:1433;databaseName=mydb;...) is also accepted.

Open the form

Go to Data → Add → SQL Server, paste the connection string, then pick datasets.

Flitch connects from its own server, not your browser, so if your database is behind a firewall or VPC security group you must allow Flitch's connector egress IP (shown in the Add Source form) on the database port, not your own IP. Publicly reachable hosts need no change.

Team-wide credential (optional)

A team admin can store one shared SQL Server credential in Settings → Data connections; new connections then default to it, with no per-connection secret.

Refresh

Refresh is off by default. Enable it to schedule a background refresh and serve from cache between runs. See Refresh.

Disconnect

Delete the connection from Data. Dashboards built from it keep their last cached data until you remove them.

Troubleshooting

Login failed for user. Check the login and password, and that the login has a user mapped in the target database with db_datareader.

Cannot open database. Verify the database name and that the login has access to it.

Connection timed out / refused. Verify host and port (default 1433), and that the egress IP is allowlisted.

TLS / certificate errors. Self-hosted servers often present a self-signed certificate; add TrustServerCertificate=true (or set SSL mode to "require"). To verify the certificate, provide the CA.