Clever Geek Handbook

SQL Server 2005 - enabling named and TCP / IP protocols?

We have a SQL Server 2005 database and currently all of our users are connecting to the database over TCP / IP.

SQL Server Configuration Manager allows you to enable both named pipes and TCP / IP connections at the same time. Is this a good idea? My question is not whether Named Pipes should be used instead of TCP / IP, but are there problems with enabling both?

One of our IT professional clients says that enabling communication with both protocols will limit the amount of bandwidth that any protocol can use - roughly 50% of the total. I would have thought that the bandwidth that TCP / IP can use would be directly tied (inversely) to the amount of traffic that Named Pipes was currently occupying (or any other type of traffic). However, this IT professional points out that the fact that we have enabled two protocols on the server artificially limits the bandwidth that TCP / IP can use. Is it correct?

I searched google but couldn't answer this question. Any help would be appreciated.

+1


source to share


2 answers


This is not true. Your thought about network traffic is correct - capacity is not "reserved".



You do not need to include named pipes unless required.

+3


source


no bandwidth limit. the problem with named pipes is that they can be quite chatty on a slow network and can have a lot of bandwidth. there is a protocol priority list to try first. but there is no internal threshold for this that I am aware of.



+2


source






More articles:


All Articles