Will have to apply SP3 to an active/passive SQL Server 2005 cluster pretty
soon and really need some advice. As far as I understand it, I have to leave
everything running as per normal and run SP3 on the active node which will
apply all the changes to both nodes, meaning obligatory downtime. Is this
right? I though there was some way of running it on the passive node, failing
over and then doing it on the other node to avoid downtime - or was that a
particular SP and it isn't always possible?
Also, once it's all run, what about the client tools - they were installed
separately on the passive node so presumable the service pack won't upgrade
them as well - or will it?
Many thanks in advance.

For SQL 2005, the procedure you outline is correct. Rolling upgrades are a
feature in SQl 2008.

You will need to run the SP on the "passive" node again to updat the client
tools. That run should be aware that it does not need to update the engine
and will only update the client tools.

Watch carefully for reboot notices when finished. They are often easy to
mistake for a "Done" notice.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP


"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

JB
http://sqlblog.com/blogs/aaron_bertr...ning-rods.aspx

http://sqlblog.com/blogs/aaron_bertr...e-updates.aspx

http://sqlblog.com/blogs/aaron_bertr...ce-pack-3.aspx


"JB" <JB (AT) discussions (DOT) microsoft.com> wrote