Description
This wait accumulates while SQL Server is waiting for the operating system to return information from the registry. This typically occurs when a user runs xp_regread or accesses the sys.dm_server_registry management view. Some values in this wait type are expected. As most registry activity from SQL is used for service and diagnostic purposes this wait is generally safe to ignore. Pre-emptive waits are different from regular (emptive) waits as their execution is controlled by an external processes such as the operating system
Resolved by
DBAs
Suggested solutions
- Run an Extended Event session with wait statistics to determine which requests are charging the wait
- Rewrite user TSQL that accesses or modifies the registry
- Check the SQL Server error log for more information
- Check the Windows Event Viewer for any disk related issues
Additional research
sys.dm_server_registry
Believe It When Microsoft Tells You Not to Use Undocumented Functions and Behaviors
Accessing Registry using XPs