Named Pipes

I am using TCP/IP for my network protocol. Is there any
need to use Named Pipes? I would like to remove this
protocol in SQL Server Network Utility.
Thank you.There's really no reason to remove it. It gives you an alternate IPC to
connect to the server with if for example we're unable to bind to the TCP
port. MDAC 2.6 clients then also have alternate means to connect to your
server. If they attempt to connect via sockets and fail, the client
transparently will attempt making a Named Pipe connection. This is of
great benefit to users who are no interested in how SQL connects, just that
it connects.
If your SQL Server is behind a firewall, the firewall should be configured
to only allow the tcp traffic for SQL. There's no additional overhead on
the server to listen on both netlibs.
If you're using a SQL Cluster then you won't be able to remove Named Pipes
after applying sp3.
831127 Named Pipes Support Cannot Be Removed on a Virtual Server That Is
http://support.microsoft.com/?id=831127
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||If the SQL instance runs in a cluster, Microsoft advises
you not to remove the support for named pipes. Otherwise,
bad things can happen (See KB article 831127).
Also check out KB 818806 -- Some Named Pipes Features Are
Not Disabled After You Disable the Named Pipes Protocol.
I hate to run into an unexpected dependency at a most
inconvenient time, and have chosen to keep both named
pipes and TCP sockets as a standard.
Do you have any specific reasons for preventing SQL Server
from listening on named pipes?
Linchi

quote:

---

>--Original Message--
>I am using TCP/IP for my network protocol. Is there any
>need to use Named Pipes? I would like to remove this
>protocol in SQL Server Network Utility.
>Thank you.
>.
>

---

|||Kevin;

quote:

---

> If they attempt to connect via sockets and fail,
> the client transparently will attempt making a
> Named Pipe connection. This is of

---

What are the exactly conditions for this 'transparent
attempt of making a Named Pipe connection' to occur? What
are scenarios in which this transparent attempt will not
be 'attempted'? I'm thinking about the situation when you
use a server alias or prefix your server name with 'tcp:'.
Linchi

quote:

---

>--Original Message--
>There's really no reason to remove it. It gives you an

---

alternate IPC to

quote:

---

>connect to the server with if for example we're unable to

---

bind to the TCP

quote:

---

>port. MDAC 2.6 clients then also have alternate means to

---

connect to your

quote:

---

>server. If they attempt to connect via sockets and fail,

---

the client

quote:

---

>transparently will attempt making a Named Pipe

---

connection. This is of

quote:

---

>great benefit to users who are no interested in how SQL

---

connects, just that

quote:

---

>it connects.
>If your SQL Server is behind a firewall, the firewall

---

should be configured

quote:

---

>to only allow the tcp traffic for SQL. There's no

---

additional overhead on

quote:

---

>the server to listen on both netlibs.
>If you're using a SQL Cluster then you won't be able to

---

remove Named Pipes

quote:

---

>after applying sp3.
>831127 Named Pipes Support Cannot Be Removed on a Virtual

---

Server That Is

quote:

---

>http://support.microsoft.com/?id=831127
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and

---

confers no rights.

quote:

---

>
>.
>

---