Skip to content

Latest commit

 

History

History
54 lines (36 loc) · 3 KB

configure-a-server-to-listen-on-an-alternate-pipe.md

File metadata and controls

54 lines (36 loc) · 3 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords
Configure a Server to Listen on an Alternate Pipe
Find out how to configure the named pipe that the SQL Server Database Engine listens on. Learn how to connect a client application to a specific named pipe.
rwestMSFT
randolphwest
03/14/2017
sql
configuration
how-to
Named Pipes [SQL Server], configuring
listening [SQL Server], pipes
pipes [SQL Server], alternate
alternate pipes [SQL Server]

Configure a Server to Listen on an Alternate Pipe

[!INCLUDE SQL Server] This topic describes how to configure a server to listen on an alternate pipe in [!INCLUDEssnoversion] by using SQL Server Configuration Manager. By default, the default instance of [!INCLUDEssDEnoversion] listens on named pipe \\.\pipe\sql\query. Named instances of [!INCLUDEssDEnoversion] and [!INCLUDEssEW] listen on other pipes.

There are three ways to connect to a specific named pipe with a client application:

  • Run the [!INCLUDEssNoVersion] Browser service on the server.

  • Create an alias on the client, specifying the named pipe.

  • Program the client to connect using a custom connection string.

Using SQL Server Configuration Manager

To configure the named pipe used by the SQL Server Database Engine

  1. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, and then click expand Protocols for <instance name>.

  2. In the details pane, right-click Named Pipes, and then click Properties.

  3. On the Protocol tab, in the Pipe Name box, type the pipe you want the [!INCLUDEssDE] to listen on, and then click OK.

  4. In the console pane, click SQL Server Services.

  5. In the details pane, right-click SQL Server (<instance name>) and then click Restart, to stop and restart [!INCLUDEssNoVersion].

When [!INCLUDEssNoVersion] is listening on an alternate pipe, there are three ways to connect to a specific named pipe with a client application:

  • Run the [!INCLUDEssNoVersion] Browser service on the server.

  • Create an alias on the client, specifying the named pipe.

  • Program the client to connect using a custom connection string.

See Also

Create or Delete a Server Alias for Use by a Client (SQL Server Configuration Manager)
Server Network Configuration