PREEMPTIVE_OS_WAITFORSINGLEOBJECT Wait Type in SQL Server

⏳Part of the SQL Server Wait Types Library, every wait type explained.Related deep dive: ASYNC_NETWORK_IO Wait TypeRelated pillar: Performance & Troubleshooting

Is It a Problem?

Read it the way you read ASYNC_NETWORK_IO: SQL Server has results and is waiting on the client. It was zero on our SQL Server 2025 lab. Get Wait Statistics does not filter it out, so if it ranks, you will see it. Sustained high values mean client applications are slow to consume data.


What It Means

Microsoft lists it as internal use only. It is the Windows WaitForSingleObject function, used to synchronise with an external client process communicating through that object, and that it is commonly seen with ASYNC_NETWORK_IO, depending on the network transport used with the client. His advice is to troubleshoot it the same way. While the call runs, the thread is in preemptive mode, outside SQL Server’s scheduler.


When It Does Matter

When it rises with ASYNC_NETWORK_IO, add the two together for the real “waiting on the application” figure. Find the waiting sessions and their programs:

SELECT
    r.session_id,
    r.wait_type,
    r.wait_time AS wait_ms,
    s.login_name,
    s.program_name,
    t.text AS running_sql
FROM sys.dm_exec_requests AS r
JOIN sys.dm_exec_sessions AS s ON s.session_id = r.session_id
OUTER APPLY sys.dm_exec_sql_text(r.sql_handle) AS t
WHERE r.wait_type LIKE N'PREEMPTIVE_OS_WAITFORSINGLEOBJECT'
ORDER BY r.wait_time DESC;

The usual fix is in the application: fetch results promptly and then process them, and ask only for the rows and columns it needs. The ASYNC_NETWORK_IO page has the full walkthrough. The baseline to monitor is the two waits’ combined share. The query needs VIEW SERVER STATE.


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. This page.
  • 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
  • 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

If this wait is climbing with ASYNC_NETWORK_IO, these are the next places to look.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *