0
Q:
Failover issues in a SQL Server 2005 mirrored database
I have a SQL Server 2005 mirrored database with a witness. Everything seems to be working OK but I am having problems in the instance a failover occurs. Once the primary server goes down, my access to the database continues normally once both servers are back up and running and the old mirror is left as the primary.

I'm using Microsoft Access through system DSN Native Client with my mirror server referenced in the DSN. The DSN passes the test for the connections. My issue is that if one of the servers goes down, I lose connection to the database. My understanding is that the connection should keep on working seamlessly. Is this correct? If not, any thoughts as to why I am having this issue?
ASKED: Jun 25 2009  4:23 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0
47070 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
What driver are you using for the DSN? If memory serves you can't create a DSN using the SQL 2005 driver and give it the failover server's information. The SQL 2008 driver includes this ability. Try downloading the SQL 2008 driver from the Microsoft site and installing that, and changing the DSN to use this new driver. Then see if there's an ability to add in the mirror database server's information.

Without putting this information into the DSN the DSN doesn't know where the other server is without the server that it knows about being online.
Last Answered: Jun 25 2009  5:02 PM GMT by Mrdenny   47070 pts.
0
0
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



0