---
title: "Connecting portier Vision Companion to Microsoft SQL Server (Correct Host Configuration)"
description: "How to connect portier Vision Companion to Microsoft SQL Server correctly, including the server format, port configuration, named instances and common troubleshooting."
url: https://help.portiervision.com/en/articles/116-connecting-portier-vision-companion-to-microsoft-sql-server-correct-host-configuration
collection: "Integrations & IT Setup"
updated: 2026-08-28
language: en
alternates: [de, fr]
---

# Connecting portier Vision Companion to Microsoft SQL Server (Correct Host Configuration)

How to connect portier Vision Companion to Microsoft SQL Server correctly, including the server format, port configuration, named instances and common troubleshooting.

## Basic Rule

The server field sits in the Companion's database configuration screen. The sign-in screen has an entry that opens the same screen.

Server and port are separated by a comma, never by a colon.

**Syntax:**

```
ServerName or IPAddress,Port
```

**Example:**

```
192.168.1.50,1433
```

**Incorrect:**

```
192.168.1.50:1433
```

* * *

## Typical Configurations

## 1\. SQL Server on the Same Machine (Local)

```
localhost,1433
```

or

```
127.0.0.1,1433
```

## 2\. SQL Server on a Network Server (Including Custom Ports)

If SQL Server runs on another machine in the network:

**Default port example:**

```
192.168.1.50,1433
```

**Custom port example (very common in customer environments):**

```
192.168.1.50,50100
```

If your SQL Server is configured with a custom static port (e.g. 50100), that port must be used.

## 3\. Named Instance (e.g. SQLEXPRESS)

For named instances, use:

```
SERVERNAME\SQLEXPRESS
```

In this scenario:

-   No port needs to be specified manually
    
-   SQL Browser (UDP 1434) is used for instance discovery
    
-   The actual database port is resolved automatically
    
-   The resolved port is often a dynamic high port (e.g. 50345)
    

You do not need to know or configure the dynamic port manually.

For clarity and simplicity, it is not recommended to combine a named instance and a fixed port in standard setups.

* * *

## Technical Requirements

To ensure a successful connection:

-   TCP/IP must be enabled in SQL Server Configuration Manager
    
-   The SQL Server port (e.g. 1433 or custom like 50100) must be open in the firewall
    
-   SQL Browser service must run when using named instances
    
-   UDP port 1434 must not be blocked (required for instance discovery)
    
-   SQL authentication must be enabled if a SQL login is used
    
-   Database user permissions must be correctly configured
    

* * *

## No ODBC Data Source Needed

The Companion connects with its own driver. You do not set up an ODBC data source for it.

The Vision desktop is a different case. On SQL Server it needs ODBC Driver 18 for SQL Server installed on the same machine. On Firebird neither application needs an ODBC driver.

* * *

## Common Issues

**Connection fails immediately**

→ Colon used instead of comma between server and port

**Connection timeout**

→ Firewall blocking SQL port (1433 or custom port)

**Named instance not found**

→ SQL Browser service not running

**Named instance not found**

→ UDP port 1434 blocked

**Login failed**

→ Incorrect credentials

**Login failed**

→ SQL authentication not enabled

**Works locally but not remotely**

→ TCP/IP disabled

**Server not found**

→ SQL Server service not running

**\`Cannot connect to database 'X'. Switching to database 'master'.\`**

→ Database offline, missing, or insufficient permissions

* * *

## Explanation of the Message

```
Cannot connect to database 'X'. Switching to database 'master'.
```

This message means:

-   The SQL Server connection itself works
    
-   But the configured target database cannot be opened
    

Typical reasons:

-   Database name is misspelled
    
-   Database was renamed or deleted
    
-   Database is set to **Offline**
    
-   Database is in **Restoring** or **Recovery** state
    
-   The SQL login has no permission for that database
    

In this case, SQL Server connects to the server but falls back to the default `master` database.

* * *

## Summary

-   Always use a comma between server and port
    
-   Use custom port numbers if configured (e.g. 50100)
    
-   For named instances, use `SERVERNAME\INSTANCENAME` only
    
-   SQL Browser handles dynamic ports automatically
    
-   Ensure UDP 1434 is open for named instances
    

**Correct:**

```
192.168.1.50,50100
```

**Incorrect:**

```
192.168.1.50:50100
```

**See also:** [Database sign-in without a stored password](https://help.portiervision.com/en/articles/124-database-sign-in-without-a-stored-password-windows-integrated-authentication.md).