I'm unfamiliar with using a connection string for the ODBC connection. We
normally create the connection using odbcad32 under System connections. When
the app launches you have a drop-down list of connections to choose so the
user just chooses the appropriate one and goes in.
Currently the connections are made using the SQL Driver. Should I remove
this connection and recreate it with the SQL Native Client and then specify
the other server as the mirror server? Or is that not what you're referring
to?
"Bob Beauchemin" wrote:
> Have you tried specifying FailoverPartner or FailoverPartnerSPN in the ODBC
> connection string? There is an example of using ODBC with Mirroring in the
> SQL Server samples, info at
> http://msdn.microsoft.com/en-us/library/aa337204.aspx .
>
> Cheers,
> Bob Beauchemin
> SQLskills
>
>
> "tuned" wrote in message
>
> > We have an application that requires an ODBC connection for it to work
> > successfully. I've set up 3 SQL 2005 servers to use db mirroring and the
> > mirroring works fine. Trouble is I'm unable to get the clients to connect
> > to
> > the mirrored server without physically creating an ODBC connection to that
> > server as well. I thought about creating a dns entry and then when the
> > roles
> > switch update dns with the new ip address. While that would work I don't
> > think it's terribly efficient and it couldn't be done pro-actively since
> > we'd
> > have to wait for a user to report there was an error. I thought about
> > creating duplicate entries with the ip addresses of the 2 servers but
> > thinking about it wasn't sure that would work either since technically the
> > failed primary (new mirror) would still respond.
> >
> > Am I missing a step in getting the clients to connect? They're all XP
> > boxes
> > and I've tried both the SQL Native Client as well as the SQL Server
> > connection.
>
> >> Stay informed about: Possible to Create ODBC to mirrored DB's 
FAQ
Search
Profile
Private Messages
Log in
