SQL Server with DBine

How to connect DBine to SQL Server and what you can do once it's connected. This page is written from what the SQL Server driver says about itself, so it matches the version of DBine you download.

Connect

In DBine, open New connection.
Pick SQL Server in the list of engines.
Fill in the fields below, press Test connection and then Save.

Default port: 1433.

General

Field	Description
Server required	Example: `localhost`
Port
Database
Authentication	Windows: current user signs in with the Windows session or, on macOS and Linux, with the Kerberos ticket (kinit user@DOMAIN). Interactive Entra ID opens the browser and supports MFA; with user and password there is no MFA. Integrated uses the Windows session (or the Kerberos ticket) with the organization's ADFS. Managed identity only works if DBine runs in Azure. Default tries, in order, the AZURE_TENANT_ID/AZURE_CLIENT_ID/AZURE_CLIENT_SECRET variables, managed identity, Azure CLI (az login) and Azure Developer CLI (azd auth login). Options: SQL Server (user and password), Windows: current user, Windows: domain username and password, Microsoft Entra ID: interactive (MFA), Microsoft Entra ID: user and password, Microsoft Entra ID: integrated (Windows), Microsoft Entra ID: service principal, Microsoft Entra ID: managed identity, Microsoft Entra ID: default, Microsoft Entra ID: access token Default: `SQL Server (user and password)`
User	With Entra ID, the account (user@domain): required with integrated, optional with interactive. With Windows, DOMAIN\user. Only with Authentication: SQL Server (user and password), Microsoft Entra ID: user and password, Windows: domain username and password, Microsoft Entra ID: interactive (MFA), Microsoft Entra ID: integrated (Windows).
Password	Kept in the system keychain, never in DBine's files. Only with Authentication: SQL Server (user and password), Microsoft Entra ID: user and password, Windows: domain username and password.
Tenant (tenant ID)	Required for the service principal. With the other methods, optional: without it, the account's tenant is used. Example: `00000000-0000-0000-0000-000000000000 or contoso.onmicrosoft.com` Only with Authentication: Microsoft Entra ID: user and password, Microsoft Entra ID: service principal, Microsoft Entra ID: interactive (MFA), Microsoft Entra ID: integrated (Windows), Microsoft Entra ID: default.
Application ID (client ID)	Service principal: the registered application's ID. Managed identity (also in default): the client ID of a user-assigned identity; empty for the system-assigned one. Otherwise, optional. Only with Authentication: Microsoft Entra ID: user and password, Microsoft Entra ID: service principal, Microsoft Entra ID: interactive (MFA), Microsoft Entra ID: integrated (Windows), Microsoft Entra ID: managed identity, Microsoft Entra ID: default.
Application secret	Kept in the system keychain, never in DBine's files. Only with Authentication: Microsoft Entra ID: service principal.
Access token	A token for https://database.windows.net/ (for example, from `az account get-access-token --resource https://database.windows.net/`). It expires in one hour. Only with Authentication: Microsoft Entra ID: access token.
Read-only	On or off.

SSH tunnel. The connection can go through an SSH server, even through a chain of bastions, with a password, a private key or the SSH agent. The server's fingerprint is checked against known_hosts or confirmed the first time.

SSL/TLS

Field	Description
Encrypt the connection (TLS)	On or off.
Trust the server certificate	On or off.

What the explorer shows

Under the connection: Databases, each with its schemas. Inside each one:

Tables
Views
Procedures
Functions
Triggers
Sequences
Synonyms
Types
Full-text catalogs
Stoplists

Query editor

The editor uses SQL, with completion for the connection's objects. Statements and commands run against the database selected in the tab.

Ready-made templates for new objects:

New view
New procedure
New function
New trigger

Tools for SQL Server

Available

Graphical execution plans
Live query profiler
Server monitor
Sessions and running queries
End a session
Locks: who blocks whom
Manual transactions (commit and rollback)
Index usage
Create databases
Drop databases
Database properties
Relations in the ER diagram
Visual designer for new objects
Rename objects
Compare and sync schemas
Clone tables
Native bulk load when migrating data
Users and permissions
Backups

Not available for SQL Server

Cancel another session's query from the sessions list

Why a tool doesn't apply to an engine, and the details of each one, are in the engine support reference.

Generated from the SQL Server driver 0.1.15, which DBine downloads the first time you connect to SQL Server.

Download DBine All engines