Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

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.

Thanks!

159 votes
Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)

We’ll send you updates on this idea

Erik Darling shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

6 comments

Sign in
(thinking…)
Sign in with: oidc
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base