client redirect

Trying just to figure out how this works...how does it know the other server to reconnect to? What does the application see, just a SQL error and the application has to redrive the TX? Can it route TX to the MIRROR and redrive it like Oracle's TAF? Thanks!

Hello

I think you are talking about the transperent Client redirection thats available if you mirror your DB and have a whitness server available.

If so, then the above feature is "only" implemented into the native SQL drivers. If you use other drivers to access SQL you wont be able to use this feature. So basically the driver itself knows that there is a whitness server, and if the main server fails, then the whitness server will tell the driver to use the mirror server which then is the new primary server.

Hope this makes sense

|||

Thanks for this response, I just need a little more details. What happens to the Transaction? Does it carry over like Oracle TAF, or does the app have to redrive it. What does the application on the primary see while the client reconnects to the other databsae, a SQL error?

Thanks1

|||Ok -- one last question -- can you list for me what the native SQL Server interfaces are. I'll assume .NET for sure. OLEDB, ODBC, JDBC, that kind of stuff..is that supported. Can you give me some examples where it redirects and doesn't redirect? Thanks..