SQL Server Performance Forum – Threads Archive
can we remove the name pipe from sql 2k cluster
Hi Allcan we remove the name pipe from SQL server 2000 cluster on windows 2003+sp1? any suggestion would be great. thanks in advance, xk
Check the following KB article… Named Pipes support cannot be removed on a virtual server that is running SQL Server 2000 SP3
http://support.microsoft.com/default.aspx?kbid=831127
MohammedU.
Moderator
SQL-Server-Performance.com
yes. but we installed SQL 2000+sp4 on win2k3+sp1. any different? thanks for quit reply.
You can take it off in that case based on the article… I never did this in my place…
Becare when you are playing with clusters….
Check what protocol cluster uses when it runs Looks alive and keep alive… MohammedU.
Moderator
SQL-Server-Performance.com
If you are using any scheduled jobs to copy the backup files or may be any network related actions using SQLAgent jobs then do not attempt to remove named pipes, as this will have knock on affect with failed jobs. I would like to know why you want to perform this change> Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
we removed named pipes from non-clustered SQL Servers based on the security requirement–our company has this security policy. thanks.
I don’t see any problem disabling it but it is advisable to check with MS before doing it on CLUSTER.
MohammedU.
Moderator
SQL-Server-Performance.com All postings are provided “AS IS†with no warranties for accuracy.
how to understand this one @http://doc.ddart.net/mssql/sql70/1_server_17.htm
SQL Server supports a subset of available network protocols when running in a clustered configuration. Clustering Service support allows failover of network addresses and names, which is supported for TCP/IP Sockets and Named Pipes. Server cluster setup, which sets up SQL Server cluster support, depends on Named Pipes. You can configure SQL Server to use TCP/IP Sockets support as long as Named Pipes is also supported. If you do not want SQL Server to listen for Named Pipes connections you can remove Named Pipes support prior to clustering, or after cluster setup by first unclustering and running SQL Server setup.
we have installed SQL 2k on win 2k3 already. i wanted to know if the named pipes could be removed after SQL Server was set up.
As suggested you can either remove the named pipes when SQL is installed first, then upgrade instance to SQL cluster and by default Virtual server listens to named-pipes protocol. If you have removed the named pipes now in future if you need to upgarde to SQL 2005 then you have to install the SQL 2005 cluster afresh,you will nto be able to upgrade from 2000 to 2005 without named pipes. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
]]>