THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is an author and engineer who enjoys building and automating data integration solutions. Andy is co-host of the Data Driven podcast. Andy is no longer updating this blog. His current blog is

Applying SQL Server Service Packs and HotFixes

This blog has moved! You can find this content at the following new location:

Published Friday, March 14, 2008 10:24 AM by andyleonard

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Ben Thul said:

I agree with all of your comments if the instance is is not clustered.  However, we've had innumerable headaches trying to install service packs for clustered instances.  We haven't found a consistent manner of application that ensures that the service pack will install correctly.  I personally had a situation after an upgrade where if the instance was on one node it reported that it was SP2, but on the other it was RTM.  I think there's some work to be done on this.

March 14, 2008 4:57 PM

andyleonard said:

Hi Ben,

  You are correct: This post is about non-clustered instances of SQL Server. That's an important distinction. Thanks for pointing it out.

:{> Andy

March 14, 2008 9:59 PM

AaronBertrand said:

I've actually had much better luck on clusters with SP2 and post-SP2 hotfixes.  SP1 was very hit or miss... mostly miss.  I had the exact same issue that Ben Thul described... one node reported SP1, the other RTM.  So, we tended to favor the SP1 node, obviously, failing back over to it whenever we had an incident that should have only incurred a single failover.  On that cluster the situation was resolved by SP2 (though in hindsight I don't know how or why it worked so smoothly).

March 18, 2008 4:21 PM

Leave a Comment


This Blog



My Latest Book:

Community Awards

Friend of Red Gate

Contact Me


Privacy Statement