Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. 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 have an issue with SQL server 2000. Its CPU utilization is high from 9.00 AM to 5.00 PM. Three applications use this server through three different instances but when the CPU utilization is high one instance is connected. I checked sp_who2 results which shows that there are many AWAITING COMMANDS and it takes up most of the CPU time. Please advise if more number of awaiting commands can cause high CPU utilization.

share|improve this question

migrated from May 15 '13 at 7:17

This question came from our site for system and network administrators.

High CPU in SQL Server is very often caused by poor indexing

Unfortunately, SQL Server 2000 lacks the tools of later versions to track these down easily

Saying that, if you run SQL Profiler you will be able to find high CPU queries and start looking at query plans to work out what indexes are missing

share|improve this answer

Your Answer


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