December 6, 2012 at 1:16 pm
I am about to upgrade our SQL-2012 Avail-Group cluster to SP1.
According to http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/827f9fbb-deb8-470a-bb12-d0c33b60a15a these are the steps to follow:
Below procedure can be followed for applying patches to SQL 2012 instances having always on
•Patch the secondary servers
•Make one secondary synchronous if there isn’t one
•Failover to that secondary
•Patch the previous primary’s server
•Failback
•If you made a secondary synchronous, make it asynchronous again
Ensure that cluster quorum is maintained during this process (e.g. by not restarting the servers simultaneously).
Is this correct? I just wanted an independent opinion please.
Thanks,
Marios
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
December 20, 2012 at 2:22 pm
Before you start installing SP1, you should read this:
A.J.
DBA with an attitude
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply