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

• Microsoft SQL Server version 6.5

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 version 6.5. This problem has been corrected in U.S. Service Pack 5a for Microsoft SQL Server version 6.5. For information about downloading and installing the latest SQL Server Service Pack, see http://support.microsoft.com/support/sql/.

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          : SSrvLock kbbug6.50 kbfix6.50.SP5 
Version           : winnt:6.5
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: April 21, 1999