Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am designing a monitoring program using HP Sitescope SIS.

The goal is detect deadlocks.

In doing so, I created a deadlock on an existing but nearly unused SQL Server 2008.

I used the following link:

Now the query has been running for over 23 hours. Would you then say the SQL Server cannot detect the deadlock?

How can I create a deadlock it can detect and kill?

What is an example output in the ERRORLOG when the deadlock is resolved?

share|improve this question
You'll know the deadlock is detected because an error will be returned to whichever session is chosen as the deadlock victim. Deadlocks are typically detected immediately, 23+ hours indicates you have not created a deadlock. Did you follow the directions in the blog precisely? – Max Vernon Mar 28 '13 at 15:28

Here is a link I read awhile back about retrieving deadlock information via extended events.

My guess is that if your query is still running then you have blocking not a deadlock. Are you sure you went back to session 1 and ran the additional update statement?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.