30 March 2007 09:53 tonyrogerson

SQL 2005 SP2 hot fix from windows update takes over 10 minutes to run!

Don't get caught out with this mess!

My client has 3 servers, 2 use database mirroring (one a principal, the other a mirror) and the third is log shipped to.

Installing the windows update on the third server worked fine and was reasonably quick, the other two - well, let's just say after 10 minutes I was getting concerned! It is not a server problem because the slowness was consistent across both servers so it's obviously some feature or something I'm using - but, do not get caught out - this hot fix is not just a tools fix!

Both servers are HP and run x64 standard of SQL 2005.

I use Database Mirroring and Service Broker on these boxes, one box (the one
that took over 10 minutes) has a second \DEV instance.

So, if you are going to do this hotfix - then allow a good window of downtime.

When will the SP2 nightmare ever end?

And still no public word or hotfix from Microsoft on the database consistency check maint plan I blogged about weeks ago.

Tony.

Filed under:

Comments

# Hot fixes are always cumulative

The one thing I learnt when I was at the MVP summit a few weeks ago was that hotfixes are always cumulative,