Post reply

Process Blocking Itself

  • December 2, 2005 at 6:50 am

    #88823

    Hi. I start a select on a remote server and on doing a sp_who on the remote server, I find that the process is blocking itself, see below. Has anyone come across this and can give me a reason why it happens. Thanks Philip

    spid   ecid   status       loginame   hostname     blk   dbname                 

    ------ ------ ------------ ------------------- ------------ ----- ----------

    64     0      sleeping     forte        KMDUDS01D    64    master          SELECT 

    64     2      sleeping     forte        KMDUDS01D    64    master          SELECT 

    64     1      sleeping     forte        KMDUDS01D    64    master          SELECT 

     

  • December 2, 2005 at 8:09 am

    #607374

    SQL server generated a parallel execution plan with 3 threads(ecid=0 to 2). 0 is the main thread. It can happen if the 3 threads have unblanced load and the main thread is waiting for other 2 threads to finish to merge the results (this is normal). Another scenario can be one of the 2 subthreads is blocked by another process and the main thread is waiting.

     

     

  • December 2, 2005 at 9:33 am

    #607424

    The "self-blocking" condition will also appear after installing SQL Server Service Pack 4.

    See "The blocked column in the sysprocesses table is populated for latch waits after you install SQL Server 2000 SP4"

    at http://support.microsoft.com/default.aspx/kb/906344

    SQL = Scarcely Qualifies as a Language

  • December 4, 2005 at 11:00 pm

    #607618

    Many thanks.

     

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply