Skip to content

configure-client-protocols.md

Latest commit

 

History

History
70 lines (46 loc) · 4.75 KB

configure-client-protocols.md

File metadata and controls

70 lines (46 loc) · 4.75 KB
title Configure Client Protocols
description Learn various ways of configuring the protocols that client applications use in SQL Server. Supported protocols include TCP/IP, named pipes, and shared memory.
author rwestMSFT
ms.author randolphwest
ms.date 08/26/2025
ms.service sql
ms.subservice configuration
ms.topic install-set-up-deploy
helpviewer_keywords
default protocols
network protocols [SQL Server], client configuration
TCP/IP [SQL Server], client protocols
disabling client protocols
ordering protocols [SQL Server]
protocols [SQL Server], order for client computers
configure client protocols
client protocols [SQL Server]
protocols [SQL Server], client configuration
default protocols, client

Configure client protocols

[!INCLUDE SQL Server]

This article describes how to configure client protocols used by client applications in [!INCLUDE ssnoversion] by using [!INCLUDE ssNoVersion] Configuration Manager. Microsoft [!INCLUDE ssNoVersion] 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 [!INCLUDE ssDE] 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 [!INCLUDE ssNoVersion] 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

  1. In [!INCLUDE ssNoVersion] Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then select Properties.

  2. Select a protocol in the Disabled Protocols box, and then select Enable, to enable a protocol.

  3. 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

  1. In [!INCLUDE ssNoVersion] Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then select Properties.

  2. 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 [!INCLUDE ssNoVersion]. The top protocol in the Enabled Protocols box is the default protocol.

    [!INCLUDE ssNoVersion] Configuration Manager creates registry entries for the server alias configurations and default client network library. However, the application doesn't install either the [!INCLUDE ssNoVersion] client network libraries or the network protocols. The [!INCLUDE ssNoVersion] client network libraries are installed during [!INCLUDE ssNoVersion] 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

  1. In [!INCLUDE ssNoVersion] Configuration Manager, expand SQL Server Native Client Configuration, right-click Client Protocols, and then select Properties.

  2. 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.

Related content