February 15, 2013 at 12:08 am
Hello,
I am having a question on configuring mirror DB on ODBC. When a Principal DB goes down the mirror DB comes up & becomes the principal DB, this will be in the case of High safety with/without automatic failover.
However, I am intreseted to know, how can we make this work on ODBC. I have configured a SQL Server Native client & created the ODBC setup, mentioned the mirror instance name as well & using a SQL Authenticated login.
The moment i do a failover on the DB side, the connection on the application side breaks inspite of mentioning the mirror instance.
I am not able to understand how can i make this work so that when the DB is failed over, the application shouldn't break, just like clustering.
Thanks
Asir
February 17, 2013 at 11:27 pm
SQL Server Gurus any solution to mu question?
February 27, 2013 at 10:37 am
If you don't see the option for Failover in the ODBC driver you need to install a newer ODBC. If I remember right you need to have at least SQL server native client 10 to support failover. When you create the new data source, select the Native 10 (or higher) driver.
You have to select a default database (of course) and then can select a mirror server. (this is on the second page of creating a new DSN)
February 27, 2013 at 11:21 am
After re-reading your original post, it looks like you may be using the correct client (As you mention you have the mirror instance set)
As a troubleshooting test I would failover the server and see if you can create a connection to the mirror only - set it as the primary server, as if there were no mirroring.
What king of authenitcation are you using NT or SQL? SQL users have to have the same SID on the principal and the mirror (otherwise they will be a db orphan when flipped to the mirror)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply