Comments
2 comments
-
Official commentHi kherrmann ,
The query shown is the SQL Database Sampler which runs every 15 seconds.
Based on https://www.sqlskills.com/help/waits/preemptive_os_lookupaccountsid/ it looks like the wait is likely occurring due to theSUSER_SNAME(db.owner_sid) [owner]which is associated with the PREEMPTIVE_OS_LOOKUPACCOUNTSID wait. It seems this can be related to performance issues with the DC's or potentially round trip time to the servers.Kind regards,
Alex
-
Thank you, Alex. I really appreciate the explanation. I was seeing similar wait types and hadn't realized that the SID lookup could be causing communication with the domain controllers. I'll investigate our DC performance and check for any network latency issues between the SQL Server and the domain environment. Thanks again for helping me understand the root cause.
https://www.sqlskills.com/help/waits/preemptive_os_lookupaccountsid/heardle
Add comment
Please sign in to leave a comment.
We have recently introduced Redgate Monitor (14.0.78) and monitor two SQL servers. While we are learning to use the messages and statistics we now run into a problem with one of the servers. The CPU disk activity is low, but the server has several waits in queue that prevent other processes from running. For now we have suspended monitoring for this server - attached a screenshot of the SQL server performance report showing the waits - what do we need to do to clear this?
