Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 441
  • Last Modified:

Examining why sql has so many processes awaiting

im looking at the results in sp_who2.   I see a lot of awaiting commands.

I have done dbcc opentran (database)
i see the oldest is our replication.

I done

select * from sysprocesses where blocked > 0
   nothing blocked.

Done sql profiler on 1204, 3605 for deadlocks - nothing

Still there are over 300-400 processes for awaiting command
Which ones are for system processes.....and must not be killed (if all of these are sa i assume that these are system or someones has hold of the sa password).

Anything else to look at.

  • 2
  • 2
2 Solutions
Awaiting command typically means that the process is complete, but the connection remains. SQL has done the work requested and is just waiting for your next statement.
Aneesh RetnakaranDatabase AdministratorCommented:
Processes with  'DbName' = ny of the system databases are System Processes (master,tempdb, msdb..)
It's possible that you started a transaction and never finished it.
Aneesh RetnakaranDatabase AdministratorCommented:
> Still there are over 300-400 processes for awaiting command
these are waiting to finish. Process state ca be running,awaiting,sleeping etc

You wont be able to kill most of the sysprocesses

better you refer Some Operating System Book to get an idea of the process.

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now