Named Pipes/TCPIP
-
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
Will Summers -
Named pipes runs better over WAN than TCP/IP. TCP/IP runs better over LAN than Named pipes.
You can try and remove it and see...
Good Hunting!AJ Ahrens
webmaster@kritter.net -
AJ, I think it's the other way around.
-
Will,
When you say much slower, it seem to me that there is a problem somewhere. The difference between TCP/IP and Named Pipes should not be as significant.
Did you verify the MDAC versions of the server on all workstations involved?
Maybe its related to the MDAC version installed. We have experience this problem in the past
.Regard,
Carl
-
By using cliconfg on the clients you can select which protocol is used. If the client needs to connect to different servers you can create aliases for each server, each with it's own protocol configuration...
Regards,
karl
Best regards
karl -
I agree with Karl. Check the client config utility on a machine whose connection is fast and configure a slower machine that way. Make sure, though, that the network library file is the same on all machines, as Carl mentioned.
Don
-
When you install SQL server you have an option to setup using a) SQL Authentication or b)SQL and Windows authentication.
Always setup using b so that you have best of both of worlds. going by the message since you are able to connect using either of the authentication modes, your server has been setup using b. Other parameters has little to contribute to this authentication.
rangark
-
If you did not write the application connecting to SQL Server it is recommended you use both Named Pipes and TCP/IP because any part of the application can call socket related functions which uses Named Pipes by default. Hope this helps.
Kind regards,
Gift Peddie
Kind regards,
Gift Peddie -
I used to agree with you on your setup recommendation; but that was the simple way, and being an Oracle DBA at heart, SQL Server was treated pretty much as a joke. Security? Who cares? The biggest advantage to me was that I could logon to the database from anywhere using SQL credentials instead of logging onto a workstation/terminal/PC as a Windows user and then connecting to the database. But simple things are simple for a reason... or perhaps I should rephrase that and say that difficult things are difficult for a reason. If you have any concerns about security (you probably should), and any exposure to hacks (you probably do) then you should be using Windows authentication. You should also be careful about what accounts you use for what services, take a "least privilege" approach to logins, and implement SSL. All of this is VERY much different than your advice to "always setup using b...".
And the poster after you is correct in stating that it is not a good idea to disable pipes if you did not write, setup, or install the application that is using them. I guess it depends again on your environment; but it is usually not a good idea to turn connectivity off without some expectation of user feedback
Cheers!
-
We modified the applications and removed Named Pipes and got about a 4% increase in query times.
Live to Throw
Throw to Live
Will Summers
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply