FIX: SPID Returns to ROLLBACK Status When You Cancel a SELECT Statement with a Parallel Plan

This article was previously published under Q269697
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 58223(SQLBUG_70)
When you cancel a query that is running a SELECT statement, which results in a parallel plan, the SPID may go into ROLLBACK status and never cancels. Any attempt to KILL the SPID is unsuccessful.

This bug only occurs on SMP servers. When this happens, you will observe the following symptoms:
  • The query never cancels.
  • All locks held by the query are maintained.
  • A SELECT * FROM sysprocesses (on the spid running the query) reports:
    waittype       lastwaittype    status0x0200         EXCHANGE        ROLLBACK						
  • Two SELECT cpu, physical_io FROM sysprocesses (on the spidrunning the query), spaced at least 15 minutes apart, reveal that the process' cpu and physical_io have not increased.
The only way to resolve this is to stop and restart the SQL Server service.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
SELECT parallel parallelism cxpacket

Article ID: 269697 - Last Review: 10/21/2013 00:03:19 - Revision: 2.1

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbcodesnippet kbfix KB269697
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)