SQL DBA Blog: Home

FT_MASTER_MERGE is recorded when a thread participating in a full-text master merge waits for the other participating threads to finish. A master merge happens when ALTER FULLTEXT CATALOG … REORGANIZE consolidates the many small full-text index fragments that accumulate through incremental population into one large index, done periodically because fewer fragments mean faster queries and…

read more

The cryptography-related preemptive waits track Windows crypto API calls, and this page covers the family: PREEMPTIVE_OS_BCRYPTIMPORTKEY, CRYPTACQUIRECONTEXT, CRYPTIMPORTKEY, CRYPTOPS, NCRYPTIMPORTKEY, VERIFYSIGNATURE, and VERIFYTRUST. Their customers are the engine’s encryption features: TDE key operations, backup encryption setting up its keys, Always Encrypted and column encryption key handling, EKM/HSM providers (where the import-key calls can genuinely leave…

read more

PWAIT_ALL_COMPONENTS_INITIALIZED appears to be a startup gate: background tasks (the SQLOS resource monitor among them, judging from its call stacks) waiting during SQL Server startup for the engine components they depend on to finish initialising. Documentation is absent, but the behaviour is consistent: it accrues around instance start and then goes quiet. Another of the…

read more

PWAIT_EXTENSIBILITY_CLEANUP_TASK is recorded by a background task belonging to the extensibility framework behind SQL Server Machine Learning Services, the Launchpad-based machinery that runs external R and Python scripts. The task sleeps in 300-second stretches between cleanup passes, and every one of those five-minute naps lands in this wait. It exists whether or not you ever…

read more

REQUEST_FOR_DEADLOCK_SEARCH is recorded by the background deadlock monitor while it waits between deadlock searches. The default interval is five seconds, and it adapts: when deadlocks are being found the monitor searches more frequently, and it relaxes back toward five seconds when they stop. So the wait is the deadlock detector’s resting heartbeat. Is It a…

read more

RESOURCE_SEMAPHORE_QUERY_COMPILE means a query is waiting for memory needed at compile time. This is different from RESOURCE_SEMAPHORE, the runtime grant wait, where a plan is already compiled and queuing for execution memory. SQL Server throttles concurrent compiles through memory gateways: an unlimited lane for cheap compiles, then progressively narrower gates for medium and large ones.…

read more

WAIT_XTP_OFFLINE_CKPT_NEW_LOG is recorded by an In-Memory OLTP (XTP) offline checkpoint thread waiting for new log records to scan. In-Memory OLTP durability works by continuously scanning the transaction log and folding changes into checkpoint file pairs (data and delta files); when the scanner catches up to the end of the log, it parks in this wait…

read more

XE_TIMER_MUTEX is recorded when a thread waits for access to the data structure holding the Extended Events engine’s timers, such as those implementing each session’s MAX_DISPATCH_LATENCY. Timer registration and firing serialise briefly on this mutex. It completes the XE timer trio with XE_TIMER_EVENT (the timers ticking) and the dispatcher waits (buffers being delivered). Is It…

read more

XTP_PREEMPTIVE_TASK appears to be a generic wait for background worker threads involved in In-Memory OLTP processing, running preemptively, so the thread stays under Windows control (state RUNNING) until its work completes. Documentation labels it internal use only. It is the XTP family’s catch-all background wait. Is It a Problem? Normally no; it accumulates as XTP…

read more