How to set up SQL Server to offer high availability during windows updates

We have a load-balanced web farm talking to a single SQL server instance. It is easy to demote web servers, install Windows updates, reboot, and then bring them back into the fold. However, we have to schedule downtime to service the SQL Server machine. What options are available to avoid such downtime?

SQL Clustering will give you the high availability that you’re looking for, as you’ll be able to apply updates to one machine, take it down for reboots, bring it back online, and ‘rinse and repeat’ for the other servers in the cluster (minimum 2).

Check more discussion of this question.

Related posts:

1. High availability in SQL Server
2. High-availability on SQL Server, cons and pros of solutions?
3. Why does Windows Automatic Updates ignore SQL Server service Packs?
4. SQL Server – Cluster vs Mirror for high availability?
5. Implementing dual control SQL updates in SQL Server