Check the sql_text and the wait_info columns to see what that session is running.
You can post emoticons.
(They both have the same : "object: 10:181575685:0 Ed Wagner SSC Guru Group: General Forum Members Points: 121717 Visits: 11354 So you probably have a f1 2012 patch 10 deadlock situation - both pieces of code are waiting on a lock to the same object.If you want to open things up that is the session you would kill, but obviously that is a sledgehammer approach and as it sounds this is starting to become a recurring issue so best to get to the bottom of the issue.Still digging around trying to resolve it, possibility missing the point!Then, if necessary, re-run the first.These could be caused by unwanted lock escalation or bad programming, but could also be from I/Os taking a long time causing locks to be held for longer than usual.5000 is a fairly small batch size in my opinion.230 is blocking 400).
You can't edit html code.
You can't send private messages.
If it were me, I would kill one and let the other run.
You can't delete your own events.What do people like to do in this situation.Select * from sysprocesses order by blocked desc Then run the below script to view what the actual blocking spid is doing.This depends on the table, on whether there is concurrent activity etc.Kill 87 This would also work when you have issues with activity monitor loading.Look at the resource associated with the lock using the DMV _os_waiting_tasks.Not blocking each other (ie session 160 is blocking 230.