Microsoft KB Archive/264689

= BUG: Parallel Process May Not Appear Blocked in the sp_who System Stored Procedure =

Article ID: 264689

Article Last Modified on 10/16/2002

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q264689



BUG #: 57975 (SQLBUG_70)



SYMPTOMS
The sp_who and sp_who2 stored procedures may not show when a process that is running with a parallel plan is blocked. Results are returned with the blk (sp_who) or BlkBy (sp_who2) showing 0 for a system process ID (SPID) that is actually blocked. Those columns should show the SPID that is blocking the affected SPID.



WORKAROUND
To work around this problem, use the sp_lock system stored procedure to see if one of the locks for the relevant SPID has a status of WAIT. To identify the blocking SPID, you must analyze the Resource that the SPID is requesting a lock for and determine what other SPID has a lock already on this resource.

For additional information about monitoring blocking, click the article number below to view the article in the Microsoft Knowledge Base:

251004 INF: How to Monitor SQL Server 7.0 Blocking



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0.

Additional query words: st proc sproc sp

Keywords: kbbug kbpending KB264689

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.