BroadSQL Download
On this page
Documentation / Connect to your database: SQL Server

Connect to SQL Server

Add the Microsoft JDBC Driver for SQL Server once, then connect with a URL that names the server and the database.

DriverNot bundled: download the Microsoft JDBC Driver for SQL Server and copy its jre11 JAR into drivers.
Type to choose in ADD CONNECTION or CONFIGSQL Server
URL formatjdbc:sqlserver://<host>:<port>;databaseName=<database>
Examplejdbc:sqlserver://dbhost:1433;databaseName=Sales;encrypt=true
Where the URL format comes fromMicrosoft Learn: Building the connection URL, checked October 17, 2026
Verified with BroadSQLNot verified with BroadSQL by the BroadSQL team: the URL format comes from Microsoft's documentation.

Steps

  1. Download the driver from Microsoft's download page. The archive holds several JAR files: copy the one whose name contains jre11 (for Java 11 and later) into drivers. Restart BroadSQL.
  2. SHOW DRIVERS; must list the Microsoft driver.
  3. ADD CONNECTION CRM_QA; (or CONFIG; on Windows), type SQL Server, URL jdbc:sqlserver://dbhost:1433;databaseName=Sales;encrypt=true, then your SQL Server login and password.
  4. PING CRM_QA;, then CONNECT CRM_QA;.

Properties are separated by ;. The port can be left out when it is the default, 1433.

Options people often need

  • Encryption and the server certificate: since version 10.2 of the driver, encrypt is true by default, and the driver validates the server's certificate (trustServerCertificate is false by default). A server without a certificate that Java trusts then refuses the connection. Microsoft's documented options are to install a valid certificate or, knowing that the certificate is then not checked, to add trustServerCertificate=true.
  • A named instance: prefer the instance's port (jdbc:sqlserver://dbhost:1435;...); otherwise ;instanceName=<name>. When both are given, the port wins.
  • Windows integrated authentication: integratedSecurity=true needs the driver's authentication DLL (mssql-jdbc_auth-<version>-<arch>.dll) on the Windows PATH. See Building the connection URL.

On SQL Server

  • DDL statements do not force a commit on SQL Server, so BroadSQL can roll them back with the transaction.
  • SET PASSWORD does not change a SQL Server password: change it in SQL Server, then update BroadSQL with EDIT CONNECTION.

Found something wrong or unclear on this page? , with the page address.