PREEMPTIVE_SB_STOPENDPOINT is recorded when a thread calls out to Windows while shutting down a Service Broker endpoint, the network listener that lets Broker exchange messages between instances. Stopping an endpoint involves OS-level teardown of its networking, done preemptively.
Endpoint stops happen at instance shutdown and when someone alters or drops the endpoint, so occurrences are inherently rare.
Is It a Problem?
No; it has not been a contention point, and its occurrences are countable lifecycle events rather than workload behaviour. Its presence in wait output simply timestamps a Broker endpoint stopping.
The pattern pairs with TERMINATE_LISTENER and the Broker startup/endpoint waits (see the consolidated Broker internals page): together they narrate endpoint lifecycles, none of them carrying performance weight.
Common Causes
- Instance shutdown stopping the Broker endpoint.
ALTER ENDPOINT ... STATE = STOPPEDor endpoint drops.
What To Do
- Filter it out of wait analysis.
- If an endpoint stop hangs (extraordinary), look at what network activity the endpoint still serves and the error log’s endpoint messages.
How To See It
Rank waits with Get-WaitStatistics; expect isolated traces around endpoint lifecycle events.
Part of the SQL Server Wait Types Library.
Related deep dive: SOS_SCHEDULER_YIELD Wait Type.
Leave a Reply