0

We are having some issues with clients getting Transaction Timeout when connecting to our clustered SQL Server 2008 R2.

To investigate the problems I have been digging into sys.dm_tran_active_transactions and a few times I saw rolled back transactions being there up til 4 hours after they were rolled back(After four hours the IIS webserver that started the transaction were restarted and they dissappeared), this was non-DTC transactions even though we do have DTC transactions as well.

So when can I expect committed/rolledback transactions to be cleared out of sys.dm_tran_active_transactions and if it is supposed to happen immediately what kind of issues could keep them "hanging" there.

Improve this question
  • Do you have transactions doing a lot of work, and getting interrupted in the middle? – Jon Seigel Apr 8 '14 at 13:28
  • Some if the ones that we're hanging was extremely simple ones doing only a single operation – jakobandersen Apr 8 '14 at 15:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.