Consider the following scenario:

  • You have an active session with the sni_trace XEvent.

  • You use the sys.dm_exec_connections DMV.

  • SQL Server has many concurrent login/logout activities.

In this scenario, you may encounter a non-yielding scheduler condition with the CONNECTION_MANAGER spinlock, and a memory dump occurs.


The workaround for this issue is to avoid running an XEvent session with the sni_trace XE in a production environment. It’s not recommended to have a long-running  XEvent session with the sni_trace XE because it can affect performance.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


This issue is fixed in the following cumulative updates for SQL Server:

About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:


Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!