"sleeping" indicates that UMS scheduler has put the thread on waiting
queue while the resource it has requested (memory, disk IO etc) becomes
available. Google "ums scheduler" and "waits" for more information on
this topic.
Hope this helps
Sal Terillo
On Jan 26, 9:07 am, "BM" wrote:
> Hi
>
> With SQL Server 2000, I have created a profiler with DB_ID = x, every things
> is ok and I can see running queries,
> But if I query sysprocesses with query like this :
>
> select sql_handle, spid, status, last_batch, waitresource
> from master.dbo.sysprocesses with(nolock)
> where DBID = x
>
> The status for all spid is always 'sleeping'
> and sql_handle = 0x0000000000000000000000000000000000000000
>
> Do you experience this before ? Do you have any idea what might cause this
> sql server behaviour ?
>
> Thank you for your help
>> Stay informed about: sysprocesses.status always return ""sleeping""