With CLUE as (Select * from Random_Thought ORDER BY Common_Sense DESC)

SQL Server thoughts, observations, and comments
posts - 52, comments - 79, trackbacks - 0

SQL 2005 Patching

I just got this question from a blog reader:

We have a SQL 2005 cluster active/passive.   Under my understanding, it would be neccesary to apply patches into a Testing environment, if working fine, proceed to the production environment... but, is it recommended to patch both nodes the same day?  or instead it would be better to patch Node1 (active) and wait some days before patching Node2 (passive)?

I would like to know your opinion on this matter !

Thanks a lot for your support.

The answer is you always must patch all nodes at once using SQL 2005.  Rolling upgrades/patches was introduced in SQL 2008  The patch process for SQL 2005 and lower is disruptive in that it takes the entire instance offline on all nodes to apply binary and internal patches.  Very risky and a major reason you test this on a practice cluster first.  When you apply the patch to the test cluster, you are not only testing the patch itself, but your procedures for applying and removing it if necessary.


Hope this helps.

Print | posted on Thursday, December 03, 2009 11:01 AM | Filed Under [ High Availability ]



# re: SQL 2005 Patching

If it's a SQL patch to the engine, then you do not need to patch the other node. SQL patches to the engine actually patch all nodes in the cluster since it's cluster-aware. However if you are instead referring to the client tools or other things that aren't cluster-aware, then you need to patch the other nodes.

If instead you are talking about Windows patches, then those should all be done one node at time but right after each other for stability reasons.
12/3/2009 5:53 PM | Tara
Comments have been closed on this topic.

Powered by:
Powered By Subtext Powered By ASP.NET