Waitopedia is a comprehensive resource of information about SQL Server waits.

The description shown below is the top answer as voted by the Spotlight community.

The charts are based on 2.1 TB of data collected from 4207 instances uploaded by 323 Spotlight users over an 8 week period.


Category: Other
SQL Server versions: 2008, 2008 R2, 2012, 2014, 2016, 2017


3 Answers


It is running a huge BI process.


I just disabled auto create and auto update statistics. Lets see if it gets better on this wait. exec sp_MSforeachdb 'ALTER DATABASE [?] SET AUTO_CREATE_STATISTICS OFF' exec sp_MSforeachdb 'ALTER DATABASE [?] SET AUTO_UPDATE_STATISTICS OFF WITH NO_WAIT'


I believe this occurs when SQL Server is committing a change to an Extended Event (Create or Alter). Spotlight uses Extended Events to monitor SQL Server and provide the information in the 'Wait Events' drilldown area. There is a know bug in SQL Server (KBKB2511963) that was supposed to fix the issue in SQL 2008 R2 SP2 CU8, but I'm still seeing it in SP3 :(

Very rare

This wait never occurs for most instances

For each of 4207 instances, we ranked PREEMPTIVE_XE_SESSIONCOMMIT on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of PREEMPTIVE_XE_SESSIONCOMMIT across the Spotlight Population

For 36 % of hours with this wait, average wait time is around 0.15 ms

For each instance, we found all the recent hours when it had a PREEMPTIVE_XE_SESSIONCOMMIT wait. We found the average latency for each of those hours.

2443 instances contributed data to this chart

Latency Distribution of PREEMPTIVE_XE_SESSIONCOMMIT across the Spotlight Population