December 23, 2023 at 12:08 am
Hi!
I have successfully installed the always-on system from your current repository, and I want to thank you for that. However, while the primary database is inaccessible, I want to be able to write to and update the secondary database. In other words, how can I automatically make the secondary database the primary one in this situation? Is it possible to set up such an architecture?
December 24, 2023 at 12:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
December 27, 2023 at 7:09 pm
Hi!
I have successfully installed the always-on system from your current repository, and I want to thank you for that. However, while the primary database is inaccessible, I want to be able to write to and update the secondary database. In other words, how can I automatically make the secondary database the primary one in this situation? Is it possible to set up such an architecture?
What situation would make your primary inaccessible? If that is true, the AG should have failed over.
This is the default architecture of an availability group. Your connections point to the listener, and when the systems failover, the listener automatically connects to whatever server is now the primary.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply