Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm looking for a way to identify top resource consuming queries in SQL Server 2000.

Is thre a way to do that other than Sql profiler or a third party monitoring tool like Quest?

share|improve this question
up vote 3 down vote accepted

There weren't a lot of system views that would give you insight in SQL 2000. The way I've done this is with Profiler/Trace, run for a few days, group/sort queries. It's a pain, but I'm not sure what other methods (other than 3rd party) you can use here.

If you have an idea of queries that run long, you can examine query plans and statistics IO for reads and the load they might be putting on your server.

share|improve this answer
That's what i thought! – Paul Oct 8 '09 at 13:42

Profiler or something like Spotlight for SQL Server from Quest will probably be your best bet.

share|improve this answer

Here's a link that has been helpful for me in this regard:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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