Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-07-10 : 22:02:57
|
| Aaron writes "I applied Service Pack 3 and all of my clients connecting to my SQL Server 7 ERP system using the TCP/IP protocol have slowed down to a crawl. Switching to Named Pipes gets the speed back to normal, but I don't want to change all 100+ client workstations throughout my WAN to Named Pipes when TCP/IP is our preferred protocol and TCP/IP was running faster than Named Pipes under Service Pack 2. Our SQL Server 7.0 servers are running on NT 4.0 SP 6a. I have tried running under NT 4.0 SP 5, Windows 2000, upgrading to MDAC 2.6 and playing around with the TCP/IP properties on the server and the client. Under each scenario, TCP/IP is fast under SQL Server SP 2 and four times slower when SP 3 is applied. What was broken in SP 3 with the TCP/IP protocol? And how can this problem be fixed short of blowing away SQL Server and reinstalling SP 2?" |
|
|
|
|
|
Slow TCP/IP with Service Pack 3