Groups | Blog | Home
all groups > sql server clustering > april 2006 >

sql server clustering : communication error when test fail over


anoni
4/27/2006 8:19:03 AM
I get microsoft odbc sql server driver tcp/ip sockets general network error
and microsoft odbc sql server driver communication link faillure errors when
I open our client app and while I did a cluster failover.

Any reasons.

Thanks.


Linchi Shea
4/27/2006 9:04:01 AM
Do you have retry logic built into your client app? You need to re-connect to
the instance.

Linchi

[quoted text, click to view]
anoni
4/27/2006 10:15:02 AM
I like the sql cluster to failover without disconnect the users or the users
would not even notice the failover. Yes. users are able to reconnect to it.
But users would lose data if they disconnected and need reconnect while the
server1 failover server2.
Is sql cluster server suppose to failover flawless?

Thanks.

[quoted text, click to view]
anoni
4/27/2006 11:26:02 AM


[quoted text, click to view]
How do I prove it is client app issue not sql cluster issue? I know the sql
cluster works fine.
[quoted text, click to view]
anoni
4/27/2006 11:43:03 AM
I got those errors pop up while I was testing and our app would not
re-connect. Users can close app then re-open it.
How do I prove it is client app issue not sql cluster issue? I know the sql
cluster works fine.

Thanks

[quoted text, click to view]
Geoff N. Hiten
4/27/2006 1:34:28 PM
A cluster failover is exactly the same as a shutdown and a restart. Users
will be disconnected. A cluster-friendly client application should
reconnect with minimum user intervention.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP



[quoted text, click to view]

Linchi Shea
4/28/2006 2:09:02 PM
When the user closes the app adn then re-opens it, it effectively reconnects.
Doesn't that in a way show the need for teh client to reconnect?

Linchi

[quoted text, click to view]
AddThis Social Bookmark Button