Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Disabling the Named Pipe Protocol in SQL Server Expand / Collapse
Author
Message
Posted Wednesday, April 6, 2011 9:52 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, November 24, 2014 5:46 AM
Points: 4,031, Visits: 7,172
Would there be any performance benefit to disabling the Shared Memory Protocol?

We have a server that executes some rather large queries then pulls the data back to it via a linked server (I know, not such a good idea but that's what we're stuck with). This process has run fairly well for years but as of a few days ago became "extremely slow"...my gut feeling tells me we've just hit a tipping point in the sheer volume of data we're querying, then pulling back through the pipe.

I've read a bit online about the different types of protocols but am unclear if there's any performance boost to changing anything.

Any thoughts?


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1089358
Posted Wednesday, April 6, 2011 10:11 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: 2 days ago @ 3:20 PM
Points: 18,064, Visits: 16,099
MyDoggieJessie (4/6/2011)
Would there be any performance benefit to disabling the Shared Memory Protocol?

We have a server that executes some rather large queries then pulls the data back to it via a linked server (I know, not such a good idea but that's what we're stuck with). This process has run fairly well for years but as of a few days ago became "extremely slow"...my gut feeling tells me we've just hit a tipping point in the sheer volume of data we're querying, then pulling back through the pipe.

I've read a bit online about the different types of protocols but am unclear if there's any performance boost to changing anything.

Any thoughts?


I don't think it will have an impact. This is a protocol and you were seeing memory pressure according to the waits if memory serves correctly.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #1089381
Posted Friday, September 28, 2012 7:20 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, September 28, 2012 8:43 AM
Points: 2, Visits: 5
Lowell (9/20/2010)
Ratheesh.K.Nair (9/19/2010)
The application wont connect to database...

For remote connection you should enable both TCP\IP and NAMED PIPES


i don't think that is true; SQL will simply use only the TCP/IP instead; disabling Named Pipes does not shut down the server or anything drastic like that;
TCP/IP is a little less chatty, but more prone to DNS errors; SQL by default gives priority to named pipe connections over TCP/IP.
take a look at this thread on the issue not too long ago; it's pretty well covered int he two pages:
http://www.sqlservercentral.com/Forums/Topic674071-146-1.aspx#bm674150


--edit: i disabled mine as proof of concept; i can connect via my localhost website, via an application, and SSMS and Linqpad, all with no problem, even tho its now disabled; i stopped and started the service as well to be sure the settings were changed.




Hi

I am an IT auditor and working on my first SQL server audit. One of my audit tests is to Verify that the Named Pipes protocol is disabled, unless there is a documented justification. My contact person told me “I disabled the Named Pipes in the SQL Native Client Config (Prod Server) but could not do so in the test and dev servers; it kept changing back to “Enabled”.”

When I followed up he told me "Given that we are not running multiple instances of SQL server on the same hardware, Names Pipes does not come into play. In other words, for the SQL Server configurations, Named Pipes does not pertain, regardless of these Named Pipe settings."

Does this sound reasonable to you SQL experts?
Post #1365855
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse