General Advise on application

Hi ,
One small doubt want to ask .
When the application is not cluster specific & when its used on cluster
(limited to connection only) .
What the applicaion has todo to get the cluster awareness thereby it won't
loose the connectivity .
Thanks
Ajay RengunthwarHi
If a client application uses the services of a clustered SQL Server, the
application needs to be able to re-connect ot the SQL Server virtual server
name after the failover occurs, and re-submit any batches that had not
completed at the time of the failover.
Very short running transaction are even more critical in this scenario.
Running a batch that takes 30 minutes is not ideal.
Regards
Mike
"Aju" wrote:
> Hi ,
> One small doubt want to ask .
> When the application is not cluster specific & when its used on cluster
> (limited to connection only) .
> What the applicaion has todo to get the cluster awareness thereby it won't
> loose the connectivity .
> Thanks
> Ajay Rengunthwar
>
>|||You need the application to trap and handle its errors. For a Clustered SQL
Server installation, if a Failover occurs, there will be a momentary,
perhaps up to 5 or 10 minutes, as the service on one machine is brought down
and then the services on the other node are brought online. It is automated
and responsive, but there is still an outage.
Your application should get connectivity errors. Look for them, pause, and
try to reconnect. Have some logic in there to attempt a few times before
giving up.
Sincerely,
Anthony Thomas
"Aju" <ajuonline@.yahoo.com> wrote in message
news:OkCDPMq3EHA.4092@.TK2MSFTNGP14.phx.gbl...
Hi ,
One small doubt want to ask .
When the application is not cluster specific & when its used on cluster
(limited to connection only) .
What the applicaion has todo to get the cluster awareness thereby it won't
loose the connectivity .
Thanks
Ajay Rengunthwarsql