Violation of Unique Index on DeadlockHash occurred

Apr 16, 2015 at 1:30 PM
Hi Andreas,

today my Deadlock Collector Job failed with the following message:
Cannot insert duplicate key row in object 'Locking.DeadLock' with unique index 'UQNCL_DeadLock_DeadlockHash'. The duplicate key value is (0x63d14706fd7be1084933e1c544eddd6e76db4482). 
For debugging purposes I removed the unique index and ended up with the seven duplicate entries in [SQL_Analysis_Data].[Locking].[DeadLock]:

Columns Plan_Handle_1 and Query_Plan_1 differ. It seems to me that SQLText_1 is some query generated by SSIS while browsing the database catalog. But I am not sure if all SQL handles relate to the deadlock situation or maybe this could be a bug, as all sql handles are fetched...just guessing?

I have got a row dump script generated by SSMS Tools but there doesn't seem to be an option to upload it here (it has 4 MB size). I would be happy to mail it to you.

Thanks in advance for checking

Martin
Apr 16, 2015 at 1:32 PM
I have just found out that I can upload a file on an issue...thus I created one. Hope that's not too bad for you.
Coordinator
Oct 2, 2015 at 9:29 PM
Hi Martin
I will upload a fixed version in the next days.
I you have something else I can test it with, I am happy to do so

Andreas
Oct 27, 2016 at 3:04 AM
Hi there,

Has this been fixed as I am still receiving the same error?