Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Named Pipes/TCPIP

Author  Topic 

ws5926
Yak Posting Veteran

88 Posts

Posted - 2005-09-01 : 15:38:58
Win 2000 Advanced Server
SQL 2000 Enterprise

My above server is running Named Pipes and TCPIP. Some machines connect with Named Pipes and some connect as TCPIP. The Named Pipes run much slower than TCPIP.

Here's my question. If I remove the Named Pipes protocol from the list, will all users connect through TCPIP?

I don't know if I remember is correctly or not, but isn't Named Pipes a protocol that was used for Win95 users connecting to SQL Server back in the 6.5 days?

Live to Throw
Throw to Live

Thrasymachus
Constraint Violating Yak Guru

483 Posts

Posted - 2005-09-02 : 08:28:20
I might try (and test) removing it from the client network utility on the clients. Something in the back of my mind is telling me you want to keep it configured on the server network utility on the server. If I remember why (server to server communication?) I will respond again to this post.

As for named pipes themselves, they used to be the only way you could connect to sql server and they hung around because it used to be not so easy to configure TCP/IP. For the sake of safety and any old legacy apps you have laying around, I would leave them enable on the server.

====================================================
Regards,
Sean Roussy

"pimpin ain't easy, but someone has to do it" -- Pimpin Whitefolks(?)
Go to Top of Page

ws5926
Yak Posting Veteran

88 Posts

Posted - 2005-09-19 : 14:25:20
We modified the applications and removed Named Pipes and got about a 4% increase in query times.

Live to Throw
Throw to Live
Go to Top of Page

rockmoose
SQL Natt Alfen

3279 Posts

Posted - 2005-09-19 : 15:53:12
The clients try to connect with the protocols in the order they are defined (top to bottom) in the cliconfg.exe utility.
The server can only respond to clients connecting with one of the server-enabled protocols.

You can remove all but TCP/IP from the server (if you only have TCP/IP connecting clients)
Test :)
Go to Top of Page
   

- Advertisement -