- Click Connection, choose SQL Server, and enter Host, Authentication, User Name, Password and optionally Initial Database.
- Write a named instance as host\INSTANCENAME and a non-default port as host,port (a comma, no spaces), as Navicat's Help Center documents.
- Navicat's SSL tab does not apply to SQL Server; turn on Use encryption on the Advanced tab instead, and only tick Trust Server Certificate if you accept skipping certificate validation.
- Azure SQL Database needs a firewall rule for your IP and outbound TCP 1433; Navicat can manage those rules from the connection's context menu.
Create the Navicat SQL Server connection
These steps apply to Navicat Premium 18, Navicat 18 for SQL Server and the free Navicat Premium Lite 18, on Windows, macOS and Linux. According to the Navicat manual:
- In the main window, click Connection.
- In the New Connection window, select SQL Server and click Next.
- On the General tab, enter a Connection Name, the Host, the Authentication method with User Name and Password, and optionally an Initial Database.
- Set encryption on the Advanced tab and, if needed, a tunnel on the SSH tab.
- Click OK.
Host, named instance and port
The SQL Server General tab has no port field. Navicat's Help Center gives the syntax to put in Host:
| You are connecting to | Host value | Notes |
|---|---|---|
| Default instance on the standard port | sqlhost.example.com | Microsoft documents that the default instance listens on TCP 1433 when TCP/IP is enabled |
| Named instance | sqlhost.example.com\SQLEXPRESS | Backslash, no spaces. Named instances use dynamic ports by default |
| Specific port | sqlhost.example.com,1439 | Comma, no spaces. Useful when a named instance has a fixed port through a firewall |
| Amazon RDS for SQL Server | The instance endpoint | The manual shows an Endpoint field for AWS instances |
Authentication options
The Authentication list in the Navicat 18 manual includes:
- SQL Server Authentication: a SQL login and password.
- Windows Authentication: SQL Server validates your Windows account. The macOS manual also lists Windows Authentication (Kerberos), and the connection guide notes that Kerberos is only available in the Enterprise and Standard editions.
- Microsoft Entra options for Azure SQL Database and SQL Managed Instance: Password, Integrated, MFA (Windows manual), Managed Identity and Service Principal.
Encryption and driver settings on the Advanced tab
Navicat's SSL tab is documented for MySQL, PostgreSQL, MariaDB, MongoDB and Redis only. For SQL Server the relevant options are on the Advanced tab:
- Use encryption: encrypts the SQL Server connection.
- Trust Server Certificate: skips validation of the server certificate. It makes self-signed certificates work, but it also removes the check that you reached the right server, so in our view it belongs on development machines only.
- Native Client Driver and Client Driver Version: choose the driver; the manual suggests switching to Legacy if the default driver does not work.
- Connection Parameters: extra connection-string keywords not exposed on any other tab; the manual's own example is
Trusted_Connection=yes;ApplicationIntent=ReadOnly;.
SSH tunnel and Azure SQL Database
The manual lists SSH tunnelling as supported for SQL Server (HTTP tunnelling is not). On the SSH tab, enable Use SSH tunnel, enter the SSH host, port (22 by default) and SSH user, choose Password, Public Key or both, and set the General tab host relative to the SSH server. The SSH server must allow TCP forwarding.
For Azure SQL Database, the manual says you cannot connect until your client IP has a firewall rule and your own firewall allows outgoing TCP on port 1433. In the Navigation pane, right-click the Azure connection and choose SQL Azure Firewall Rules to add your address range. Error 40615 is the symptom when the rule is missing.
Common Navicat SQL Server connection errors
| Error | Usual cause | Fix |
|---|---|---|
| 18456 Login failed for user | Wrong password, disabled login, or SQL authentication not enabled on the server | Check the login and the server authentication mode |
| 10061 Target machine actively refused it | Nothing listening on that host and port | Check that TCP/IP is enabled and the port is right (host,port) |
| 53 Server not found | Wrong host or instance name, or the port is blocked | Check host\INSTANCENAME, SQL Server Browser and the firewall |
| 4060 Cannot open database | The Initial Database does not exist or the login has no user in it | Correct Initial Database or create a user for the login |
| 40615 Cannot open server (Azure SQL) | No firewall rule for your IP | Add a rule with SQL Azure Firewall Rules |
Frequently asked questions
How do I specify a port for SQL Server in Navicat?
Add it to the Host after a comma with no spaces, for example 192.0.2.10,1439. The SQL Server General tab has no separate port field.
How do I connect Navicat to a named SQL Server instance such as SQLEXPRESS?
Use a backslash in the Host: servername\SQLEXPRESS, with no spaces. If the instance has a fixed port, you can use servername,port instead.
Does Navicat support SSL for SQL Server?
Not through the SSL tab, which covers MySQL, PostgreSQL, MariaDB, MongoDB and Redis. For SQL Server, enable Use encryption on the Advanced tab, with Trust Server Certificate only if you accept skipping certificate validation.
Can Navicat on a Mac use Windows Authentication for SQL Server?
The macOS manual lists Windows Authentication and Windows Authentication (Kerberos). Kerberos authentication is only available in the Enterprise and Standard editions.
Why can Navicat not connect to Azure SQL Database?
Usually because the server firewall has no rule for your IP, or your network blocks outbound TCP 1433. Add a rule from SQL Azure Firewall Rules in Navicat or in the Azure portal.
Sources
- Navicat 18 manual: Establish Connection
- Navicat 18 manual (Windows): General Settings
- Navicat 18 manual (macOS): General Settings
- Navicat 18 manual: Advanced Settings
- Navicat 18 manual: SSL
- Navicat 18 manual: SSH Tunneling
- Navicat Help Center: How can I connect to a SQL Server Instance?
- Navicat Help Center: How can I specify the port for SQL Server connection?
- Navicat Premium Lite product page
- Microsoft Learn: Configure a server to listen on a specific TCP port
Checked 8 October 2026.
How we research tool guides: our editorial method. CodeWithSQL earns nothing from the vendors mentioned.