June 24, 2004 at 10:10 pm
For one of our databases, we use an Access97 front end to a SQL 2000 backend. Until recently, we've set up our ODBC connection to use named pipes as it gave us a significant speed improvement over the TCPIP setting.
Today, however, the database was slow. Nothing has supposedly changed on the network and our database has not experienced any unusual activity so I looked at the ODBC connection. All of the sudden, I can't keep the named pipes connection to hold and it reverts back to TCPIP. There are no error messages along the way but records that used to load instantly are now taking 1 sec to load.
My specialty is not networking so I am a bit out of my league here but it seems odd to me that this has changed w/o anyone being able to explain why.
TIA. Laura
June 25, 2004 at 7:08 am
If you have SQL Server Client Network Utility installed on that machine check to see if the Named Pipes Library is disabled (General tab) or missing (Network Libraries tab).
June 28, 2004 at 7:24 am
Have there been recent changes in your network?
Named pipes are not routable, so perhaps they don't work anymore?
Best regards
karl
June 28, 2004 at 7:33 am
Our network administrator tells me that nothing has changed but something must have changed in order for named pipes to no longer work. The only thing I discovered the other day was that the network admin upgraded BackupExec on the server and the MDAC got upgraded from 2.7 to 2.8. Most of the client machines are using 2.6 or 2.7 but that shouldn't cause this problem as far as I am aware.
June 28, 2004 at 7:40 am
On the SQL-Server, using SQL-Server Network-configuration, is named pipes still activated?
Best regards
karl
June 28, 2004 at 7:47 am
Yes, it is still activated.
June 28, 2004 at 7:47 am
Yes, it is still activated.
June 28, 2004 at 8:09 am
On my system users connect with Named pipes one day, TCP/IP the next and named pipes the following day. At the moment I have 2 users on named pipes and 40 on TCP/IP. Tomorrow it will be different users on named pipes. I believe (but may be wrong) that the client PC tries to connect with named pipes as a preference, but uses TCP/IP if the named pipes connection doesn't get a response in time. Unfortunately, I have not found anything that allows me to change the network protocol settings, such as preferred protocol (the one to try using first). Named pipes put alot more traffic over the network then tcp/ip so I would rather my users connect with tcp/ip. But I still want to use named pipes, hehe.
If you want the clients to only connect with named pipes, disable tcp/ip in the server properties on the server (Network configuration button). But if your problem is due to higher network traffic from users of other systems. You may find your users still get a slow response from named pipes.
Regards
Peter
June 28, 2004 at 5:48 pm
If you run the cliconfg.exe utility on the client with administrative or power user rights you can see what will be the protocol used to connect to the server. (And change it). Make an alias using NP for the server you want o connect to if you haven't got one already
If you do not have sufficient rights on the regkey where it is updated, the setting will either not change or may revert to what ever is the default, during the current user session or on next client login.
Named pipes has issues with routing but unless your network guys are throttling the network, it should go as fast as or better than TCP/IP once it connects.
Check out BOL for "Named Pipes Client Connections"
DB
The systems fine with no users loggged in. Can we keep it that way ?br>
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply