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'm investigating a blocking issue that I believe is related to implicit transactions not being committed or rolled back.

How can I identify connections that have turned the implicit transactions setting on?

share|improve this question
up vote 4 down vote accepted

Well to answer your specific question, you should be able to see that in the existing connections and audit:login events in SQL Server Profiler/Tracing.

I would actually start by trying to investigate who the blockers are and then dig in, however. You may have better luck in actually tracking down the blockers if they actively block and you see the blocking in action.

You should be able to do that by either querying the dynamic management view - sys.dm_os_waiting_tasks (described here) or installing and using Adam Machanic's sp_whoisactive (a procedure I recommend you install anyway)

share|improve this answer
Thank you for the response. We were able to determine that implicit transactions were indeed our problem. – Cory Nov 15 '11 at 16:15

Try this:

select s.session_id,
from sys.dm_tran_session_transactions s
    inner join sys.dm_tran_active_transactions t ON s.transaction_id = t.transaction_id
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.