SQL 7 runs with dual processors runs at 90% after a week or so. NT4
platform with nothing else running. I have used Profiler to watch for
Lock:Timeouts. Is there something else I should be auditing? I am not sure
I know what to do or what it all means. If BOL has something on the subject
I'm just missing it.

And whatever the solution is, can it be applied directly to SQL 2000?

Any Help Out There?
Hugh


The information in this electronic mail message is sender's business
Confidential and may be legally privileged. It is intended solely for the
addressee(s). Access to this Internet electronic mail message by anyone
else is unauthorized. If you are not the intended recipient, any
disclosure, copying, distribution or any action taken or omitted to be taken
in reliance on it is prohibited and may be unlawful.
The sender believes that this E-mail and any attachments were free of any
virus, worm, Trojan horse, and/or malicious code when sent. This message and
its attachments could have been infected during transmission. By reading
the message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action about viruses and
other defects. Galileo International is not liable for any loss or damage
arising in any way from this message or its attachments.


MS Sql Server LazyDBA home page