Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to:
SQL Server
This article 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.
Configure all client applications to use the same network protocol by setting the protocol order in SQL Server Configuration Manager.
Configure a single client application to use a different network protocol by creating an alias. For more information, see Create or delete a server alias for use by a client.
Some client applications, such as sqlcmd.exe, can specify the protocol as part of the connection string. For more information, see Connect to SQL Server with sqlcmd.
Use SQL Server Configuration Manager
Enable or disable a client protocol
In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then select Properties.
Select a protocol in the Disabled Protocols box, and then select Enable, to enable a protocol.
Select a protocol in the Enabled Protocols box, and then select Disable, to disable a protocol.
Change the default protocol or the protocol order for client computers
In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then select Properties.
In the Enabled Protocols box, select 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.
SQL Server Configuration Manager creates registry entries for the server alias configurations and default client network library. However, the application doesn't 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 might not be available as part of Windows Setup. For more information about installing these network protocols, see the vendor documentation.
Configure a client to use TCP/IP
In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then select Properties.
In the Enabled Protocols box, select 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.