Every few weeks sp_who2 shows a chain of "spid"-s all blocked by one spid. (We usually ask the person with the main "spid" to log off)
1. Is there any way to be more proactive, to look for likely issues before the user informs us there is a problem? (As I mentioned everything can be fine for weeks then, for no apparent reason, all *&*^% breaks loose.)
2. If not what are the minimal sql perfmon options to use to great a trace of the events leading up to the blocking.
TIA,
edm2