Is It a Problem?
The call itself is quick when Windows is healthy; our SQL Server 2025 lab had about 4,700 waits totalling 13 seconds in a day. Get Wait Statistics does not filter it out, so if it ranks, you will see it. Its useful angle is volume: growth means something is writing to the Windows event log at pace, and the messages are the real finding.
What It Means
Microsoft lists it as internal use only. It is the Windows ReportEvent function, which writes an entry to the Windows event log. SQL Server writes significant error log messages there, along with messages from RAISERROR ... WITH LOG and login auditing. While the call runs, the thread is in preemptive mode, outside SQL Server’s scheduler.
When It Does Matter
When it rises, read the messages: the SQL Server error log and the Application event log around that time name the source, such as a burst of failed logins, a recurring error, or chatty WITH LOG calls. Fix the source. Get Error Log Patterns groups repeated messages. The baseline to monitor is the event log write rate staying steady.
The PREEMPTIVE_OS Call Waits
Each of these is SQL Server calling a Windows function outside the file and security groups: networking, pipes, the registry, the event log, DLLs and the cluster. The time is spent in Windows. If one is near the top of your waits, read it next to the waits that usually matter.
- Network waitsDNS and sockets. GETADDRINFO name lookups and Winsock calls; slow DNS shows here.Worth a look when it climbs
- PREEMPTIVE_OS_PIPEOPSPipes. Windows pipe functions, such as xp_cmdshell reading its command output.Worth a look when it climbs
- PREEMPTIVE_OS_WAITFORSINGLEOBJECTClient sync. Synchronising with an external client process; often seen with ASYNC_NETWORK_IO.Worth a look when it climbs
- PREEMPTIVE_OS_QUERYREGISTRYRegistry. Windows registry functions.Worth a look when it climbs
- PREEMPTIVE_OS_REPORTEVENTEvent log. The Windows ReportEvent function, writing to the event log.Worth a look when it climbs. This page.
- PREEMPTIVE_OS_GETPROCADDRESSXP entry points. Finding an extended stored procedure’s address in its DLL.Worth a look when it climbs
- Library waitsDLL loading. Loading and unloading DLLs in the SQL Server process.Usually noise
- Cluster waitsFailover cluster. Windows failover cluster API calls.Usually noise
- Miscellaneous waitsEverything else. The remaining single-call waits, such as VSS, FILESTREAM device and service calls.Worth a look when it climbs
Where To Go Next
PREEMPTIVE_OS_REPORTEVENT is background noise at normal volumes. If you are chasing a real problem, start with the waits that cost you time.
- Get Error Log Patterns, repeated messages grouped.
- The waits that usually matter, ranked, with what each one is telling you.
- Performance & Troubleshooting, the scripts and guides for this part of the stack.
Leave a Reply