Timeline for AlwaysOn Availability Group Forced Failover
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 9:05 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 20, 2014 at 15:53 | comment | added | Thomas Stringer | @TDPSQL_Newbie No problem! Always glad to help. | |
| Mar 20, 2014 at 15:52 | vote | accept | TDPSQL_Newbie | ||
| Mar 20, 2014 at 15:51 | comment | added | TDPSQL_Newbie | Many thanks Thomas, used this link. Appreciate your input. | |
| Mar 20, 2014 at 15:23 | comment | added | Thomas Stringer | @TDPSQL_Newbie See my edit. And definitely follow the "note/warning/disclaimer". | |
| Mar 20, 2014 at 15:22 | history | edited | Thomas Stringer | CC BY-SA 3.0 |
added 719 characters in body
|
| Mar 20, 2014 at 15:07 | comment | added | TDPSQL_Newbie | For the availability group I am only able to remove the active primary db not the secondary - remove gets greyed out. do I delete the availability group resume the db and then recreate the availability group? | |
| Mar 20, 2014 at 14:58 | comment | added | TDPSQL_Newbie | Hi Thomas Thank you for the response. Please can you break this one step further for me. This is a test and there are no txns since the failover. When it shows as not synchronized. What do I need to do to resume the database.Do I need to delete the availability group? I do not see the suspended state... | |
| Mar 20, 2014 at 14:20 | history | edited | Thomas Stringer | CC BY-SA 3.0 |
edited body
|
| Mar 20, 2014 at 13:42 | history | answered | Thomas Stringer | CC BY-SA 3.0 |