September 19, 2010 at 4:44 am
Hi All,
I need one help, In one of the interview the interviewer asked me if you are using web based application as a front end. What happened when we disable the named pipe? Will Application still work or will give any problem.
Thanks in advance!!
September 19, 2010 at 11:20 pm
The application wont connect to database...
For remote connection you should enable both TCP\IP and NAMED PIPES
September 20, 2010 at 12:51 am
Ratheesh.K.Nair (9/19/2010)
The application wont connect to database...For remote connection you should enable both TCP\IP and NAMED PIPES
Hi
Ratheesh.K.Nair
May we use both TCP\IP and NAMED PIPES at the same time? if Yes please let us know how?
Thanks
Ali
MCTS SQL Server2k8
September 20, 2010 at 2:29 am
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.
Lowell
September 20, 2010 at 7:12 am
Thanks Lowell
September 21, 2010 at 3:01 am
If you want to use Full Text indexing then you will need Named Pipes.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
September 24, 2010 at 12:13 pm
EdVassie (9/21/2010)
If you want to use Full Text indexing then you will need Named Pipes.
Not true. We successfully use Full-Text under SQL Server 2005 and SQL Server 2008 R2 with Named Pipes disabled.
September 27, 2010 at 3:21 am
We successfully use Full-Text under SQL Server 2005 and SQL Server 2008 R2 with Named Pipes disabled
Interesting. Maybe the Microsoft documentation is wrong. See http://msdn.microsoft.com/en-us/library/ms345189.aspx for the reference
The SQL Server service acts as a named pipe server for the FDHOST Launcher service client
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
September 27, 2010 at 6:45 am
EdVassie (9/27/2010)
We successfully use Full-Text under SQL Server 2005 and SQL Server 2008 R2 with Named Pipes disabled
Interesting. Maybe the Microsoft documentation is wrong. See http://msdn.microsoft.com/en-us/library/ms345189.aspx for the reference
The SQL Server service acts as a named pipe server for the FDHOST Launcher service client
I would expect that it would use Shared Memory considering that all of the processes are running on the same machine.
September 27, 2010 at 11:23 am
Ratheesh.K.Nair (9/19/2010)
The application wont connect to database...For remote connection you should enable both TCP\IP and NAMED PIPES
Simply not true. I have worked with SQL Server 2005 farms that have a multitude of web servers connecting in to the databases and we had named pipes disabled in those instances.
Named pipes and TCP\IP both have networking advantages, TCP\IP is more resilient and generally preferred. There's reams of info on this if you look around
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 6, 2011 at 9:52 am
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; Theyll drag you down to their level and beat you with experience
April 6, 2011 at 10:11 am
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[/url]
Learn Extended Events
September 28, 2012 at 7:20 am
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?
July 10, 2017 at 5:58 am
Check for Telnet <ServerName> <PortNumber> , it should be open.(Scree will go blank)
Regards
Chandan Gupta
July 12, 2017 at 4:24 am
Chandan.mssqldba - Monday, July 10, 2017 5:58 AMCheck for Telnet <ServerName> <PortNumber> , it should be open.(Scree will go blank)
Regards
Chandan Gupta
this thread is 6 years old!!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply