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:
1. Running Profiler
2. 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.dm_exec_plan_attributes or sys.query_context_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.
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.