There could be many possible reasons. There isn't enough info from your
description to offer anything more specific except that before you recycle
the server it'd be useful to collect more info on the state and consumption
of the resources.
Also, I don't think this is specific to clustering. If you had just taken
teh SQL resource offline and online (i.e. recycle the instance), you probably
would have seen the same behavior.
Linchi
[quoted text, click to view] "Cedric" wrote:
> Current topology
> - Sql Server 2000 on Windows 2003 Cluster
>
> The Client access to the database started to degrade on a particular
> database, when we tried to access the SQL Enterprise Manager - it result in
> connection failed. however other databases were available.
>
> Being in a cluster we moved the SQL engine to the other node and killed all
> the idle processes.
> The Database was then accessible... What could be the cause of such an issue?
> i;ll be most grateful if you could give me a preventive action also...
> thanks
>
>
> --