named pipes?

Hello
Which is the difference between using named pipes and TCP/IP?
Is it possible to enable TCP/IP and disable named pipes at the same time for
the server communication?
What happens if I disable named pipes?
Tanx
Alejandra Parra
Mexico
Named Pipes is MUCH slower, unless it is between servers, where it runs in
the kernal. I believe it has to do with the ability to queue requests - but
I'm not sure about that.
I usually disable named pipes on my servers. Otherwise people create DSNs
to connect and indicate Named Pipes, then wonder why the application is so
slow.
"Alejandra Parra" wrote:

> Hello
> Which is the difference between using named pipes and TCP/IP?
> Is it possible to enable TCP/IP and disable named pipes at the same time for
> the server communication?
> What happens if I disable named pipes?
> Tanx
> Alejandra Parra
> Mexico
>
>
|||"Alejandra Parra" <alparrita@.hotmail.com> wrote in message
news:OzuMkbRkEHA.2908@.tk2msftngp13.phx.gbl...

> Which is the difference between using named pipes and TCP/IP?
SQL Server BOL has a good write-up on the differences between these two
libraries see 'Named Pipes vs. TCP/IP Sockets'.

> Is it possible to enable TCP/IP and disable named pipes at the same time
for
> the server communication?
Yes, just make sure the network libraries are set up the same way on the
client side.

> What happens if I disable named pipes?
Most likely nothing... I've seen some old utilities and software dependent
on named pipes, however it's unlikely to effect you. As always, test before
deploying to production.
Steve