Hi,
We have a bought in VB6 application that uses ODBC to connect to a sql
server 2000 database. We have moved the database to a windows 2k3 cluster and
now need to look at the client surviving failover.

Basically if I have the client connected to the virtual instance then fail
the "live" server in the cluster the instance switches but the client errors
on next query. The only way back is to restart the client.

The "use the failover sql server on primary sql server failure" option
within the odbc configuration looked to be a possibility but it is greyed out
and research suggests that this is an old option that is no longer available.

It looks like my only option is to go back to the supplier and get them to
add error handling and retries into the client, or has anyone else
encountered this problem and found another way round it?

Thanks in Advance

Hi

Re-coding to be cluster aware is currently your only option.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Nik" <Nik@discussions.microsoft.com> wrote in message
news:2E5264EA-07A6-4D2E-AA09-CF63F81516C4@microsoft.com...
> Hi,
> We have a bought in VB6 application that uses ODBC to connect to a sql
> server 2000 database. We have moved the database to a windows 2k3 cluster
> and
> now need to look at the client surviving failover.
>
> Basically if I have the client connected to the virtual instance then fail
> the "live" server in the cluster the instance switches but the client
> errors
> on next query. The only way back is to restart the client.
>
> The "use the failover sql server on primary sql server failure" option
> within the odbc configuration looked to be a possibility but it is greyed
> out
> and research suggests that this is an old option that is no longer
> available.
>
> It looks like my only option is to go back to the supplier and get them to
> add error handling and retries into the client, or has anyone else
> encountered this problem and found another way round it?
>
> Thanks in Advance
>

Thanks Mike,
That's what I thought but it's nice (?) to have it confirmed

Regards,
Nik

"Mike Epprecht (SQL MVP)" wrote:

> Hi
>
> Re-coding to be cluster aware is currently your only option.
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program: http://www.microsoft.com/mvp
>
> Blog: http://www.msmvps.com/epprecht/
>
> "Nik" <Nik@discussions.microsoft.com> wrote in message
> news:2E5264EA-07A6-4D2E-AA09-CF63F81516C4@microsoft.com...
> > Hi,
> > We have a bought in VB6 application that uses ODBC to connect to a sql
> > server 2000 database. We have moved the database to a windows 2k3 cluster
> > and
> > now need to look at the client surviving failover.
> >
> > Basically if I have the client connected to the virtual instance then fail
> > the "live" server in the cluster the instance switches but the client
> > errors
> > on next query. The only way back is to restart the client.
> >
> > The "use the failover sql server on primary sql server failure" option
> > within the odbc configuration looked to be a possibility but it is greyed
> > out
> > and research suggests that this is an old option that is no longer
> > available.
> >
> > It looks like my only option is to go back to the supplier and get them to
> > add error handling and retries into the client, or has anyone else
> > encountered this problem and found another way round it?
> >
> > Thanks in Advance
> >
>
>
>