1

I'm trying to troubleshoot some performance problems on our SQL2000 production server. I ran DBCC SQLPERF(waitstats) and noticed the stats hasn't been cleared in a long time. So I cleared them and did some refreshing and noticed after only a few minutes, OLEDB reported a signal wait time in the order of hundreds of millions of milliseconds. How is this possible?

Improve this question
1
  • 1
    Time to Get rid of SQL Server 2000 as it is an unsupported version.
    – Kin Shah
    May 1, 2014 at 15:20

1 Answer 1

Reset to default
1

The signal wait time is aggregated across all cores. Any system with more than one core can have total signal waits longer than the last time you clear the wait stats.

Improve this answer
0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.