How to minimize downtime on SQL Server patching

#31

Then it is clear two nodes, apply service packs, reboot pasive nodes, move
instances, reboot newly passive nodes one at a time, and finally settle out
the instances. Note that each instance will be down while the service pack
is appplied. No way around that in SQL 2005.

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

"Mauricio Tamayo Ortega" <MauricioTamayoOrtega (AT) discussions (DOT) microsoft.com>
wrote in message news:72C0A992-5446-4525-840C-9CDD96A24D1B (AT) microsoft (DOT) com...

Quote:

Sorry, I need to do it in SQL 2005

"Geoff N. Hiten" wrote:

SQL 2008.

New feature is rolling upgrades. You upgrade a "passive" node (or more
than
one in your case), Fail over the targeted instance to that node set,
upgrade
the formerly active node (and any remaining passive nodes). Repeat for
each
instance.

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

"Mauricio Tamayo Ortega" <MauricioTamayoOrtega (AT) discussions (DOT) microsoft.com
wrote in message
news:671343E6-960B-4B6D-99C3-EE526E87CC2C (AT) microsoft (DOT) com...
Hi,

Is there any way to install SQL Server patches without causing
downtime?
We
want to patch a 5-way A/A/A/A/A cluster but we find that always the
hotfix
setup stops the instances during patching.

Thanks for any idea/suggestion/recommendation.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

How to minimize downtime on SQL Server patching

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: How to minimize downtime on SQL Server patching - 10-09-2008 , 11:20 AM