So, my employer (may) be frowning on after-hours work (even though it's a *bad* thing to take down a production SQL during the day to reboot from OS updates that they require to be installed by a certain date) and I'm looking to get some options lined up to resolve this.
While a SQL cluster would be a solution, they started migrating to a VMWare environment before I started, and just recently decomissioned the last physical SQL servers (in a cluster no less) a couple months ago.
So, I thought of AAGs. It sounds like this would let me do the OS updates (which on my SQL servers I am responsible for) by the following method:
1. Update the replica (which would not be configured for read-only access)
2. Reboot the replica
3. Wait for the DBs to re-synch
4. Manually (planned) failover the AAG DBs to the replica, making it the Primary
5. Repeat steps 1-4, replacing "replica" with "primary" (although technically the former primary would now be the replica because of step 4)
6. Go home at my normally scheduled time, and only connect in to work if something breaks...
I've set up a very basic AAG at home in a VM environment without to much hassle, so that part I think I could manage.
I'm also presuming that any SQL Agent jobs would need to be configured on *both* hosts, as you can't make system DBs part of an AAG (one downside compared to a cluster, at least.)
Am I on the right track? Or at least a reasonable one, if this becomes a requirement?