How do I fix mismatch SP2+Hotfix to SQL Cluster Node

Background: I have an Active-Passive Cluster environment hosting 24x7 critical hospital databases. I noticed that SP2+patch is missing on Passive node and planning to apply missing sp2+patch on Passive Node. This is a PRODUCTION and Critical so want to verify all my steps well in advance.

                                               VIRTUAL
--------- Node-1------------            --------- Node-2------------

Windows 2003 Enterprise SP2       Windows 2003 Enterrpise SP2
SQL 2005 Enterprise, SP2+Patch   SQL 2005 Enterprise, SP1
Active                                                              Passive

PLAN-A
1) Full Backups of all databases (System and Users).
2) Move groups on Node-2 using Cluster Administrator
3) Pause Node-1 using Cluster Administrator
4) Apply SP2 on Node-2.  SP2 is cluster aware and this will search for Passive (Node-1 now) but it is in PAUSED so will complete only on NODE-2.
5) Continue for Patch in the same manner on Node-2.
6) Check Version on Node-2.
7) Resume-Node Node-1 using Cluster Administrator
8) Move groups on Node-1 using Cluster Administrator

PLAN-B
1) Full Backups of all databases (System and Users).
2) Move groups on Node-2 using Cluster Administrator
3) Apply SP2 on Node-2.  SP2 is cluster aware and this will search for Passive (Node-1) and it is already up to date and will do nothing but will apply sp2 only on NODE-2.
4) Continue for Patch in the same manner on Node-2.
5) Check Version on Node-2.
6) Move groups on Node-1 using Cluster Administrator
7) Test results.

PLAN-C
1) Full Backups of all databases (System and Users).
2) Go to Node-1 (Active) and apply SP3. SP3 is cluster aware and will complete on Passive first and then active.
3) Check version on Active-Node-1.
4) Move groups on Node-2 using Cluster Administrator
5) Check version on Node-2 Active now.
6) I can remove SP3 only in add/remove program any time if anything goes wrong.

Questions:
1) Can I remove sp2 or patch only from Node-2 if anything goes wrong using add/remove program? I think this is not ROLLOVER as in SQL 2008.
2) Which plan is 100%?
3) Please add expert comments only.

Thank you very much in advance for everyone.
SSHARMA2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
SP on sql cluster should be applied while being connected on the cluster instance.
patching a individual node should not work?

unless you only patched a client tools?

>I noticed that SP2+patch is missing on Passive node
can you clarify how you identified that?
0
SSHARMA2Author Commented:
Hi - Genius
I tested in the following way
a) I ran the following query when I was connected to Node-1 ( It gave me SP2+Patch info);
SELECT SERVERPROPERTY('productversion') AS VersionNumber,
       SERVERPROPERTY ('productlevel') AS ProductLevel,
       SERVERPROPERTY ('edition') AS Edition

b) Failover on Node-2 and ran same query and got SP1 info.
0
Guy Hengel [angelIII / a3]Billing EngineerCommented:
apart from that "problem", you might consider getting to SP3:
http://support.microsoft.com/kb/934749

that article also shows the "how to" apply the patches.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

SSHARMA2Author Commented:
Hi - angellll,
Thanks for your prompt reply.

I know SP3 is perfect solution but considering overall situation I will concentrate on Workaround 'Method 1' (http://support.microsoft.com/kb/934749): Sounds like my PLAN-B.
 
a) Fail over to the new node.
b) Pause other nodes by using Cluster Administrator.
c) Install SQL Server 2005 SP2 on the new node.
d) Apply SQL Server 2005 SP2 Cumulative Update 6 and the appropriate hotfixes as applicable to the scenario on the new node.
e) Start the nodes that you paused
0
Guy Hengel [angelIII / a3]Billing EngineerCommented:
yes, except that you planned to play safe with:
1) Full Backups of all databases (System and Users).
which is really good!
0
SSHARMA2Author Commented:
We have next week schedule to complete this task and I will post my comments after that. Thanks.
0
SSHARMA2Author Commented:
This has been rescheduled and will take place after three weeks.
0
SSHARMA2Author Commented:
This has been completed successfully. Thanks for suggestion and verification.
0
SSHARMA2Author Commented:
This was nice experience that we can ask/verify solution before apply on PROD.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.