Export (0) Print
Expand All

How to: Configure Client Protocols (SQL Server Configuration Manager)

Use SQL Server Client Configuration to enable or disable protocols used by client applications. To view client protocols, in the console pane, expand SQL Server Native Client Configuration, and then click Client Protocols.

The details pane shows you the names of the protocols and the order in which the client tries them when attempting to connect to a server. You can also see whether the protocol is enabled or disabled (status) and obtain more information about the protocol file.

Right-click a protocol to access a context menu with the following commands:

  • Enable, which allows SQL Server to use the selected protocol.

  • Disable, which prevents SQL Server from using the selected protocol.

  • Order which opens the Client Protocol Properties dialog box.

To enable or disable a client protocol

  1. In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then click Properties.

  2. Click a protocol in the Disabled Protocols box, and then click Enable, to enable a protocol.

  3. Click a protocol in the Enabled Protocols box, and then click Disable, to disable a protocol.

To change the default protocol or the protocol order for client computers

  1. In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then click Properties.

  2. In the Enabled Protocols box, click Move Up or Move Down, to change the order in which protocols are tried, when attempting to connect to SQL Server. The top protocol in the Enabled Protocols box is the default protocol.

In the console pane of SQL Server Configuration Manager, click Aliases to see a list of currently configured aliases in the details pane. Click the column name in the header to sort the display. By creating server aliases, your client computer can connect to multiple servers using different network protocols, without having to specify the protocol and connection details for each one. In addition, you can also have different network protocols enabled all the time, even if you only need to use them occasionally. If you have configured the server to listen on a non-default port number or named pipe, and you have disabled the SQL Server Browser service, create an alias that specifies the new port number or named pipe.

Alias Name

The name of the alias. Client applications connects to this name.

Server

The server instance associated with this alias.

Protocol

The protocol designated for the connection.

Parameters

Any additional connections string information, such as port number or pipe name.

To create an alias

  1. In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Aliases, and then click New Alias.

  2. In the Alias Name box, type the name of the alias. Client applications use this name when they connect.

  3. In the Server box, type the name or IP address of a server. For a named instance append the instance name.

  4. In the Protocol box, select the protocol used for this alias. Selecting a protocol, changes the title of the optional properties box to Port No, Pipe Name, VIA Parameters, or Connection String.

For samples of each type of alias with valid and invalid combinations, see the following topics:

NoteNote

If a configured alias is connecting to the wrong server or instance, disable and then reenable the associated network protocol. Doing this clears any cached connection information and allows the client to connect correctly.

Important noteImportant

The VIA protocol is deprecated. This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.

Community Additions

ADD
Show:
© 2014 Microsoft