Windows 2003 SP1 and SQL 2000 SP3 - performance now cut in half!!!

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Drinian - 23 Aug 2005 04:07 GMT

Ever since installing W2K3 SP1 on our SQL 2000 cluster out performance has
detiorated dramatically. We're seeing execution times 100 to 200% longer
(slower) and huge increase in the amount of blocking and overall locks.

We've tried updating statictics and are working with MS now but they don't
really seem to have any idea what would cause this. Literally nothing else
has changed and I can trace back to the minute the performance problems
starting concurrently with the first reboot after the SP1 install.

Does anyone have any ideas?

thanks!

Reply to this Message

Luca Bianchi - 23 Aug 2005 08:34 GMT

> Ever since installing W2K3 SP1 on our SQL 2000 cluster out
> performance has detiorated dramatically. We're seeing execution
> times 100 to 200% longer (slower) and huge increase in the amount of
> blocking and overall locks.

Are you using one of the sw listed in "List of applications where a
regression was found during the application compatibility tests" section?

http://support.microsoft.com/?id=896367

I experienced a similar problem with an older version of ArcServe Backup
(Computer Associate).

> Does anyone have any ideas?
>
> thanks!

Bye

Signature

Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com

Reply to this Message

Mike Epprecht (SQL MVP) - 23 Aug 2005 13:59 GMT

Hi

Check that your drivers work with SP1 correctly. Quite often HBA and NIC
drivers need to be updated for a SP.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

> Ever since installing W2K3 SP1 on our SQL 2000 cluster out performance has
> detiorated dramatically. We're seeing execution times 100 to 200% longer
[quoted text clipped - 8 lines]
>
> thanks!

Reply to this Message

Uttam Parui[MS] - 24 Aug 2005 05:42 GMT

With any service packs, hotfixes, security patches, it is not recommended to apply it on production without testing it on a test environment.

It appears that SP1 was directly applied to the production cluster. Was Win2K3SP1 installed on both nodes (assuming a 2node cluster) or just one node? Since you have
a cluster, you can do rolling upgrade. The steps to apply sp1 on say node 1 will something like

1. Open Cluster Administrator, right-click Node 1, and then click Pause Node.
2. Right-click Node 1, click Move Group for all groups owned by Node 1 to move all groups to Node 2.
3. Install the Service Pack 1 on Node 1, and then restart the computer.
4. Check the System event log for errors. If you find any errors, troubleshoot them before continuing this process.
5. In Cluster Administrator, right-click Node 1, and then click Resume Node.
6. Right-click Node 2, and then click Move Group for all groups owned by Node 2 to move all groups to Node 1.

Test everything. If your results are not as expected like you saw, you failover the groups to Node 2 (which is still on RTM) and everything should be fine. Then you can
create a plan to backoff from SP1 on Node 1. If the tests are succesful, you can repeat the steps and apply SP1 on node 2.

Best Regards,

Uttam Parui
Microsoft Corporation

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Reply to this Message