How to establish a connection with SQL Server instance configured to listen on non-standard port

Overview

You can customize the Port number on which your SQL Server instance is configured as may be required by your organization’s security guidelines and policies.

This article explains the steps to establish a connection with SQL Server instance configured to listen on non-standard port (customized port number).

Who should read this?

  • Database Administrators
  • System Administrators
  • TopTeam Administrators

Method 1. Establish a connection with SQL Server instance configured to listen on non-standard port using Management Console

For TopTeam Application Server

Open TopTeam Application Server Management Console, go to Database Settings

wpid33809-media_1494502687751.png

Enter “<<Server Name>>, <<Port number>>” separated by a comma to connect TopTeam Application Server to SQL Server configured to listen on non-standard port.

For TopTeam Web Server

Open TopTeam Web Server Management Console, go to Database Settings

wpid33810-media_1494502907673.png

Enter “<<Server Name>>, <<Port number>>” separated by a comma to connect TopTeam Web Server to SQL Server configured to listen on non-standard port.

Method 2. Establish a connection with SQL Server instance configured to listen on non-standard port using Alias

Step 1. Open SQL Server Configuration Manager

wpid33811-media_1494503477867.png

SQL Server Configuration Manager opens

wpid33813-media_1494585460720.png

Step 2. Expand SQL Native Client Configuration

wpid33814-media_1494585528231.png

Step 3. Create a new Alias

wpid33815-media_1494585624571.png

Step 4. Enter Alias details and click Apply

wpid33816-media_1494585749970.png

Alias is created with non-standard port

wpid33817-media_1494585879426.png

NOTE: In case you have SQL Native Client Configuration for both 32bit and 64bit, then follow the same process to create an Alias for 64bit configuration.

Step 5. Open TopTeam Application Server Management Console, go to Database Settings

wpid33812-media_1494564334479.png

Revised: May 12th, 2017