Named Pipes or TCP/IP 1

[LCannon]

Which is better for connecting to SQL from clients? Named Pipes or TCP/IP?

 

[JayKusch]

TCP/IP ... that, by defualt, is the way SS sets up its connections Thanks

J. Kusch

 

[JayKusch]

Below are quotes from the book "Microsoft SQL Server 2000 Administrator's Companion" (hard copy version). They show that named pipes cause signficantly more overhead with network traffic and prevent connection pooling from being effective.

Page 239:
"Named Pipes"
...
"Although named pipes is an efficient protocol, it is not usually used for large networks because it does not support routing and gateways. It is also not preferred for use with a slower network. Named pipes requires significantly more interaction between the server and the client that do other protocols, such as TCP/IP."

Page 572:
"connections based on ... named pipes are generally slow. Using named pipes also poses problems for connection pooling. ... most implementations [of named pipes] use challenge/response or basic authentication from the Web server to enforce individual connections into SQL Server. This effectively negates any performance improvement connection pooling might have offered." Thanks

J. Kusch

 

[LCannon]

That is most helpful, Jay. Really appricate it.