Managing Integrations
Add, review, reconnect, and secure your data source integrations.
Microsoft SQL Server
Connect a Microsoft SQL Server database and import tables or results from custom queries.
Connect a Microsoft SQL Server database and choose the data you want to use in Dashbreeze. You can import complete database tables or use a read-only query to create a table with only the results you need.
Important:Dashbreeze reads data from your SQL Server database but does not change or delete it. Your connection details are encrypted and are not stored in the browser.
What do you need to connect Microsoft SQL Server?
- A SQL Server database that accepts external connections — self-hosted or from a managed provider such as Azure SQL Database or Amazon RDS
- The host, port, database name, username, and password, or a single connection string such as
mssql://username:password@hostname:1433/database - A database user with read access to the tables you want to import — a dedicated read-only user is strongly recommended
SQL Server Authentication must be enabled because Dashbreeze connects with a database username and password rather than a Windows account. Any firewall or security group must also allow Dashbreeze to reach the database port.
How does the database connection work?
- When Dashbreeze connects: when you browse tables, preview a query, or refresh imported data.
- What dashboards use: an imported copy of your data. Opening a dashboard does not query SQL Server again.
- What Dashbreeze can access: only tables the connected user has permission to read.
- Custom queries: one read-only
SELECTorWITHstatement.
How do you connect a SQL Server database?
- Select Connect Database (or Add Database if you already have one connected) from the SQL Server table setup.
- Give the integration a recognizable name and, optionally, a description.
- Choose Direct Connection to fill in the host, port, database name, username, and password individually, or Connection URI to paste a single connection string instead.
- Select Test Connection to confirm Dashbreeze can reach the database before anything is saved.
- Select Connect.
Direct Connection
Use separate fields for the host, port, database name, username, and password.
Connection URI
Paste one complete connection string from your database provider.
What Test Connection checks:It confirms that the database address and credentials work. Table access still depends on the permissions given to the connected user.
How do you choose what to import?
Select your saved database connection, then choose one of these options:
Pick a Table
Choose one or more existing tables. Each one becomes a separate table in Dashbreeze.
Best when the source table already contains what you need.
Write Custom Query
Join tables, filter rows, rename fields, or calculate values with one read-only query.
Best when you need a more focused result.
Previewing a query:Execute Query displays up to 50 rows so you can check the result. Creating or syncing the table runs the complete query.
Do you need an SSH tunnel?
Use Connect through an SSH tunnel only if your database is reached through a bastion or jump host. Keep the main host and port fields set to the database address, then enter the SSH server details and authenticate with a password or private key.
The SSH host is not the SQL Server host. It is the server Dashbreeze connects through to reach SQL Server. Your database administrator can tell you whether a tunnel is required and provide the SSH host, port, username, and authentication method.
How does SQL Server data stay updated?
A SQL Server connection is live. Open the imported table and use Sync data for an immediate refresh, or enable automatic updates and choose a schedule.
Each refresh runs the selected table import or saved custom query again and replaces the previous imported copy with the latest result. It does not change the source database.
Before changing the source:Renaming or removing source tables and columns can stop a refresh or affect transformations, charts, and metrics that use them. Keep names stable when possible, and review dependent dashboard content after a schema change.
