1

I need some guidance please. An application is going through migration and the processes seem to be quite cpu intensive. CPU utilisation on the server is very high - in the 90's.

The headblocker session appears to be processing, as the 'Last Batch' column is current and no waiting time reported.

There are however, a number of sessions which are in AWAITING COMMAND.

Microsoft doc says not to kill these sessions:

Use KILL carefully, especially when critical processes are running. You can't kill your own process. You also shouldn't kill the following processes: AWAITING COMMAND

I would appreciate some suggestions on how to proceed please.

Thank you.

Improve this question
11
  • 1
    What value do you see under open_tran_count for those sessions?
    – SqlWorldWide
    Oct 21, 2021 at 10:57
  • To clarify, cpu on which server is high? And what exactly do you mean by that - is there cpu queueing or are there just processes doing work? 'AWAITING COMMAND' means the DB session is waiting to be told what to do - the application server hasn’t given it a command yet. Is it possible that your application is doing work? What exactly is your migration doing?
    – Andrew Sayer
    Oct 21, 2021 at 11:53
  • @SqlWorldWide, thanks for your response. open_tran_count value is different for each session as reported by sp_whoisactive. ranges from 0-2
    – PTL_SQL
    Oct 21, 2021 at 12:38
  • @Andrew Sayer, thanks for your response. The host server cpu resource is under pressure with SQL using up to 97% as seen in Task Manager Processes.
    – PTL_SQL
    Oct 21, 2021 at 12:41
  • @Andrew Sayer, avg_task_count is currently 21 while avg_runnable_tasks_count is 8
    – PTL_SQL
    Oct 21, 2021 at 12:44

0

Reset to default

Your Answer

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

Browse other questions tagged or ask your own question.