Sample Header Ad - 728x90

Many sessions AWAITING COMMAND

1 vote
0 answers
3848 views
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](https://learn.microsoft.com/en-us/sql/t-sql/language-elements/kill-transact-sql?view=sql-server-ver15) 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.
Asked by PTL_SQL (427 rep)
Oct 21, 2021, 10:00 AM
Last activity: Oct 21, 2021, 12:34 PM