SQL Server Performance


Discussion in 'General DBA Questions' started by rinuv, Sep 29, 2005.

  1. rinuv New Member


    When I ran the sp_who2 command on one of my SQL servers, under the command column I got some processes that showed up as 'Conditional'. What does 'Conditional' exactly mean? Does that mean its stuck in a loop? We pushed some new code couple of days ago and our CPU is beginning to peg out at 100%. I ran the profiler to identify the culprit and we might have identfied it. Is there anything else I can try?

    Thanks in advance for any input.
  2. dineshasanka Moderator

  3. rinuv New Member

    I have noticed that the CPU spikes up to 100% for about 10 to 15 minutes and then comes back to normal (30 to 40%). When it spikes up, I run a sp_who2 and notices processes with runnable status and a command of conditional. When it comes back to normal, I run a sp_who2 and notices that the conditional processes are either sleeping or gone. However, when the CPU returns to normal, the db response time is still very slow. I stopped and started SQL and the response time was good. But when the CPU went back to 100% and came back, the response time was slow again. We're trying to modify the procedure that we think is causing the issue. In the meantime, is there anything that I can look or do that will help? I have tried everything that I know of.

    Thanks again for any assistance.

Share This Page