Configure Client Protocols

Applies to: SQL Server

This topic describes how to configure client protocols used by client applications in SQL Server by using SQL Server Configuration Manager. Microsoft SQL Server supports client communication with the TCP/IP network protocol and the named pipes protocol. The shared memory protocol is also available if the client is connecting to an instance of the Database Engine on the same computer. There are three common methods of selecting the protocol.

Using SQL Server Configuration Manager

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.

    Important

    SQL Server Configuration Manager creates registry entries for the server alias configurations and default client network library. However, the application does not install either the SQL Server client network libraries or the network protocols. The SQL Server client network libraries are installed during SQL Server Setup; the network protocols are installed as part of Microsoft Windows Setup (or through Networks in Control Panel). A particular network protocol may not be available as part of Windows Setup. For more information about installing these network protocols, see the vendor documentation.

To configure a client to use TCP/IP

  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 the up and down arrows 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.

The shared memory protocol is enabled separately by checking the Enabled Shared Memory Protocol box.

See Also

Configure the remote login timeout Server Configuration Option