Timeline for Network Maintenance and High Availability Group Prep
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2019 at 21:58 | comment | added | HandyD | Best practise would be to change replicas to Synchronous Commit, failover to a replica that won't be affected by any outage from the change, perform your change and then failback after the change once replicas are synchronised, and finally reset any Asynchronous replicas that were changed to Synchronous. | |
| Jul 23, 2019 at 18:36 | vote | accept | WadeH | ||
| Jul 23, 2019 at 13:11 | comment | added | WadeH | Thank you for your reply. Would this be considered the best practice in this scenario or is there something else I should consider? | |
| Jul 23, 2019 at 0:15 | review | Low quality posts | |||
| Jul 23, 2019 at 4:01 | |||||
| Jul 22, 2019 at 23:58 | history | answered | HandyD | CC BY-SA 4.0 |