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] "Linchi Shea" wrote:
> Do you have retry logic built into your client app? You need to re-connect to
> the instance.
>
> Linchi
>
> "anoni" wrote:
>
> > 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.
> >
> >
[quoted text, click to view] "Geoff N. Hiten" wrote:
> 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.
> 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.
[quoted text, click to view] > --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
>
> "anoni" <anoni@discussions.microsoft.com> wrote in message
> news:316C153A-BA62-437C-A9B2-AA4F36CB4AA9@microsoft.com...
> >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.
> >
> > "Linchi Shea" wrote:
> >
> >> Do you have retry logic built into your client app? You need to
> >> re-connect to
> >> the instance.
> >>
> >> Linchi
> >>
> >> "anoni" wrote:
> >>
> >> > 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.
> >> >
> >> >
> >> >
>
>
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] "anoni" wrote:
>
>
> "Geoff N. Hiten" wrote:
>
> > 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.
>
> > 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.
> > --
> > Geoff N. Hiten
> > Senior Database Administrator
> > Microsoft SQL Server MVP
> >
> >
> >
> > "anoni" <anoni@discussions.microsoft.com> wrote in message
> > news:316C153A-BA62-437C-A9B2-AA4F36CB4AA9@microsoft.com...
> > >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.
> > >
> > > "Linchi Shea" wrote:
> > >
> > >> Do you have retry logic built into your client app? You need to
> > >> re-connect to
> > >> the instance.
> > >>
> > >> Linchi
> > >>
> > >> "anoni" wrote:
> > >>
> > >> > 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.
> > >> >
> > >> >
> > >> >
> >
> >
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] "anoni" <anoni@discussions.microsoft.com> wrote in message
news:316C153A-BA62-437C-A9B2-AA4F36CB4AA9@microsoft.com...
>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.
>
> "Linchi Shea" wrote:
>
>> Do you have retry logic built into your client app? You need to
>> re-connect to
>> the instance.
>>
>> Linchi
>>
>> "anoni" wrote:
>>
>> > 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.
>> >
>> >
>> >
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] "anoni" wrote:
> 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
>
> "anoni" wrote:
>
> >
> >
> > "Geoff N. Hiten" wrote:
> >
> > > 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.
> >
> > > 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.
> > > --
> > > Geoff N. Hiten
> > > Senior Database Administrator
> > > Microsoft SQL Server MVP
> > >
> > >
> > >
> > > "anoni" <anoni@discussions.microsoft.com> wrote in message
> > > news:316C153A-BA62-437C-A9B2-AA4F36CB4AA9@microsoft.com...
> > > >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.
> > > >
> > > > "Linchi Shea" wrote:
> > > >
> > > >> Do you have retry logic built into your client app? You need to
> > > >> re-connect to
> > > >> the instance.
> > > >>
> > > >> Linchi
> > > >>
> > > >> "anoni" wrote:
> > > >>
> > > >> > 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.
> > > >> >
> > > >> >
> > > >> >
> > >
> > >
Don't see what you're looking for? Try a search.