May 17, 2014 at 7:21 am
We have two instances running in mirrored configuration. Two databases are being used by the same web application.
In the case a failover occurs on one of these databases, the situation is that one database is principal on server A, and the other database is principal on server B.
After the failover, the application won't work because it seems it's looking for the principle databases on only one of the servers.
The connection strings are identical except for the database name.
I read that the client will cache the failover partner, so maybe this happens on a more generic level and not on a per-database level.
What can I do to resolve such a situation?
Thanks in advance.
Regards, Serge
June 10, 2014 at 8:30 am
serge 83317 (5/17/2014)
We have two instances running in mirrored configuration. Two databases are being used by the same web application.In the case a failover occurs on one of these databases, the situation is that one database is principal on server A, and the other database is principal on server B.
After the failover, the application won't work because it seems it's looking for the principle databases on only one of the servers.
The connection strings are identical except for the database name.
I read that the client will cache the failover partner, so maybe this happens on a more generic level and not on a per-database level.
What can I do to resolve such a situation?
Thanks in advance.
Regards, Serge
Why A and B are not together? It would be easier if you keep them on same server and if that server goes down, then both move to the mirrored one. Unless you want to minimize the impact of both being down.
Anyway... when you're using Mirroring, you need to specify the failover partner on your connection string. Check this link: Database Mirroring in SQL Server
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply