May 7, 2022 at 11:14 pm
In our environment we have about 10 Always on Set up. The application has configured to connect using listener. The applications are didn't hard coded with server (They are using listner name) still whenever we did the fail over, few applications are not working on one server.
May 9, 2022 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.
May 12, 2022 at 5:28 pm
In our environment we have about 10 Always on Set up. The application has configured to connect using listener. The applications are didn't hard coded with server (They are using listner name) still whenever we did the fail over, few applications are not working on one server.
Is there an actual error message you are getting???
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/
May 12, 2022 at 6:25 pm
Your applications need to have connection retry logic written into them.
When a failover happens it doesn’t transfer the active sessions so you need to ensure you reopen the session after failover.
But as Michael has said an error or something more to go on would be good.
June 2, 2022 at 2:47 am
We find the issue. The secondary replica is not read intend. So The default DB is user database in Primary but default DB is Master in Secondary replica. When we did the fail over it is connecting to the Master DB & it caused the app failures.
June 7, 2022 at 12:17 am
Secondary replicas as I understand have read intent off by default. Did you make this change in the application or the database ?
----------------------------------------------------
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply