Easier identification of Implicit Transactions
Lots of ORMs let developers choose to enable implicit transactions, but there's no easy way to identity them without:
- Running Profiler
- Using the existing_connection XE session
Though it's a SET option, it's not included in the plan XML where SET options are identified, nor is it in sys.dmexecplanattributes or sys.querycontext_settings.
Using implicit transactions haphazardly can lead to some pretty nasty blocking chains. It should be much easier to identify when they're in use.
Oh tell me whyyyyyyy.... Do we build implicit transactions in the sky? Oh tell me why.... SQL Server does not identify Oh tell me why (with tribute to the original of Ian Van Dahl)
Fully agree !!
couldn't agree more on this. It has caused a lot of deadlocks
Steven Rao commented
We are having tons of deadlocks because of this option.
Ignacio Salom commented
Salvador Lancaster commented
Faldie Bassardien commented
I agree with Eric Darling & Max Vernon. Please make it easy to identify.
Max Vernon commented
Sirens should sound on the server whenever someone enables implicit transactions.