May 10, 2012 at 3:46 am
Hi all - Until we get to SQL 2012 it looks like i am going to have to set up a mirroring configuration for 2 of our SQL servers. Although I am fairly comfortable with setting this up for a particular DB and creation of endpoints etc, the one area I am a little confused about is configuring the app connection string should it fail over to the mirror.
I have been reading about different connection types, but am confused between Native access, ADO etc. How can I tell what my current app is using, and how can I ensure the app will automatically use the mirror should it fail over?
Thanks for any pointers
May 10, 2012 at 5:39 am
Kwisatz78 (5/10/2012)
Hi all - Until we get to SQL 2012 it looks like i am going to have to set up a mirroring configuration for 2 of our SQL servers. Although I am fairly comfortable with setting this up for a particular DB and creation of endpoints etc, the one area I am a little confused about is configuring the app connection string should it fail over to the mirror.I have been reading about different connection types, but am confused between Native access, ADO etc. How can I tell what my current app is using, and how can I ensure the app will automatically use the mirror should it fail over?
Thanks for any pointers
If your application is a .Net application, then it can take the advantage of automatic failover feature of mirroring. You just need to add failover_partner="YourSecondaryServer" in the application connection string. Once you added this entry in the connection string, application will automatically try to connect to your secondary server when ever it does not find the primary server to connect.
I am not sure if the same can be done in the applications that are written in the languages other than .Net.
May 11, 2012 at 2:18 am
Hi thanks for the reply, I will check out what out app is using.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply