Timeline for Creating AlwaysOn Availiability Group & Listener not showing on second node with T-SQL?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Apr 5, 2022 at 22:04 | history | edited | mustaccio | CC BY-SA 4.0 |
Removed cruft; formatted list
|
| S Apr 5, 2022 at 22:04 | history | suggested | pppery | CC BY-SA 4.0 |
Removed cruft; formatted list
|
| Apr 5, 2022 at 21:29 | review | Suggested edits | |||
| S Apr 5, 2022 at 22:04 | |||||
| Apr 5, 2022 at 19:46 | vote | accept | JammyShaw | ||
| Apr 5, 2022 at 19:46 | vote | accept | JammyShaw | ||
| Apr 5, 2022 at 19:46 | |||||
| Apr 5, 2022 at 19:35 | vote | accept | JammyShaw | ||
| Apr 5, 2022 at 19:46 | |||||
| Apr 5, 2022 at 16:39 | comment | added | JammyShaw | @BenThul I am pretty much seeing everything on the 1st node so the AlwaysOn AG, the listener, the database in a syncronised state, the green ticket to say it is syncronising, etc. I haven't actually tried to force failover, I will do that now and come back to you. :) MBuschi If Bens advice doesn't work, I will give this a try :) Thank you both! Will keep you updated. | |
| Apr 5, 2022 at 13:03 | answer | added | Sean Gallardy | timeline score: 0 | |
| Apr 5, 2022 at 7:18 | comment | added | MBuschi | if you don't see replicated databases on the secondary but you see the AG groups, try to run this: ALTER AVAILABILITY GROUP [<AGName>] GRANT CREATE ANY DATABASE. | |
| Apr 5, 2022 at 2:04 | comment | added | Ben Thul | What, specifically, are you seeing on node 1 that you aren't seeing on node 2? Does a failover of the AG change that? | |
| Apr 5, 2022 at 2:02 | history | migrated | from stackoverflow.com (revisions) | ||
| Apr 4, 2022 at 18:04 | history | asked | JammyShaw | CC BY-SA 4.0 |