Hello, I am looking for sanity check on a SQL upgrade approach. Starting point is a clustering and mirroring deployment based on SQL 2008 SP3. The intent is to upgrade to SQL 2012 RTM. SQL 2012 SP1 is no option, because the application using SQL services is not yet compliant.
I am aware of http://msdn.microsoft.com/en-us/library/bb677181.aspx. However, the requirement to upgrade the mirror server first and do a manual fail over to upgrade the former principal, does not play nice with the needs of the application using SQL services. This approach would require to apply a set of configuration tasks in order to direct the app tier to the upgraded mirror/ new principal.
I am therefore wondering if the following upgrade sequence is supported as well:
Deployment design:
- Primary site: 1x failover cluster with two nodes (active/ passive)
- Secondary site: 1x standalone mirror server
- Mirroring configuration: high safety without automatic failover
Upgrade approach:
1. Upgrade standalone mirror
2. Upgrade passive node_2 on failover cluster
3. Fail over on failover cluster from active node_1 to passive node_2. Upgrade the original active, now passive node_1
4. Fail back on failover cluster to node_1 which will become again active node
5. Mirroring resumes automatically
Please post a brief confirmation, if this approach is supported.
Thanks in advance.