|MS SQL Server 2012 - DBA Articles|
Configure a Server to Listen on an Alternate Pipe
Named Pipes is an authenticated protocol. This means that any time a user attempts to open a connection to the SQL Server via Named Pipes, the Windows NT authentication process occurs. This is important to remember because Named Pipes is also the default protocol when installing SQL Server. Named Pipes is required to support SQL Server's integrated security option. It's also worth noting that Named Pipes connects very fast - much faster than the other protocols.
You can configure the named pipe protocol to listen on a designated named pipe. By default, the default instance of SQL Server Database Engine listens on pipe \\.\pipe\sql\query for the default instance and \\.\pipe\MSSQL$\sql\query for a named instance. The Database Engine can only listen on one named pipe, but you can change the pipe to another name if you wish. The SQL Server Browser service helps clients identify the pipe when they connect.1
This topic describes how to configure a server to listen on an alternate pipe in SQL Server 2012 by using SQL Server Configuration Manager. By default, the default instance of SQL Server Database Engine listens on named pipe \\.\pipe\sql\query. Named instances of SQL Server Database Engine and SQL Server Compact listen on other pipes.
In Windows 8 Environment, to open SQL Server Configuration Manager, in the Search charm, under Apps, type SQLServerManager11.msc (for SQL Server 2012) or SQLServerManager10.msc for (for SQL Server 2008), and then press Enter Key.
In SQL Server Configuration Manager, in the left pane, click SQL Server Services.
In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, and then click expand Protocols for .
In the details pane, right-click Named Pipes, and then click Properties.
On the Protocol tab, in the Pipe Name box, type the pipe you want the Database Engine to listen on.
Typed prem word end of the existing Pipe Name.
To continue, click OK. System displays warning message window. Just click OK.
In the console pane, click SQL Server Services.
In the details pane, right-click SQL Server () and then click Restart, to stop and restart SQL Server.
More Reference URL: http://msdn.microsoft.com/en-us/library/ms189321%28v=sql.110%29.aspx
* * * * *