Microsoft KB Archive/181244

= FIX: INSERT..SELECT with IGNORE_DUP_ROW on a Clustered Index Stops Responding =

Article ID: 181244

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q181244



BUG #: 17814



SYMPTOMS
INSERT..SELECT with IGNORE_DUP_ROW on a clustered index stops responding, and the insert never completes. Examination of sysprocesses shows the spid to be sleeping, with a waittype of 0x0013. No indication of blocking nor deadlocking is present; effectively, the insert has blocked itself.



WORKAROUND
To work around this problem, replace the clustered index with a non- clustered index. Alternatively, removing the IGNORE_DUP_ROW option from the clustered index may solve the problem.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.



MORE INFORMATION
The spid will not respond to a KILL statement; SQL Server must be shut down. Depending of the size of the insert, there may be a lengthy recovery process for the database when SQL Server is restarted.

Additional query words: deadlock sleep kill stop client undetected block sqlserver

Keywords: kbbug kbfix KB181244

-

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

© Microsoft Corporation. All rights reserved.