April 18, 2008 at 4:32 am
Hi at all,
a simple question. Do someone know what kind of processes contain this table?
...explaining better...
If my application 'xxx', connect to my Database and exec a simple query, this operation (cmd = SELECT) and my application result in the sysprocesses table. And there, nothing wrong...
But when my application has finished to elaborate the query, this process (just executed, signed with cmd = AWAITING COMMAND) is traced again... until my application is connected.
Why? Can I interprete the connection like a SQL process (tracet into sysprocess table)?
Another question, (i've tryed to find something around the web, but nothing exhaustive...) what's the meaning for:
SELECT
AWAITING COMMAND
LAZY WRITER
...and so on?
Thx
Andrea
April 18, 2008 at 5:11 am
Basically,
After your application has done what it needs to do the connection is not instantly dropped. The connection remains open in the application pool. As such, AWAITING COMMAND is just an indication that there's an open connection on the SQL Server and it's doing nothing. It's just sitting there waiting for a command of some type.
If you opened a query window in query analyzer and you checked in sysprocesses for that particular spid you'd see the same thing, AWAITING COMMAND.
Commands like LAZY WRITER, CHECKPOINT SLEEP, LOCK MONITOR, etc... are just background tasks that you shouldn't need to worry about.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply