Hi! My application retries the last SQL query when a conncetion went down then came backup again. This worked well with standalone SQL Server 2000.
But in a SQL Sever 2000 clustering, if one of the nodes went out then came back up again, the dead connection attribute SQL_ATTR_CONNECTION_DEAD was never set, therefore the connection was not usable yet it was not "dead".
How can I detect a dead connection in a clustering situation? I was hoping the cluster itself would automatically replace the bad one with a valid connection but I guess this might be either too mcuh to ask for or maybe I missed a cluster setup parameter.
Any hints or tips are appreciated!
Regards, Nancy
But in a SQL Sever 2000 clustering, if one of the nodes went out then came back up again, the dead connection attribute SQL_ATTR_CONNECTION_DEAD was never set, therefore the connection was not usable yet it was not "dead".
How can I detect a dead connection in a clustering situation? I was hoping the cluster itself would automatically replace the bad one with a valid connection but I guess this might be either too mcuh to ask for or maybe I missed a cluster setup parameter.
Any hints or tips are appreciated!
Regards, Nancy
