January 10, 2011 at 11:09 am
Can anyone explain what these wait types are?
PREEMPTIVE_OS_AUTHENTICATIONOPS
PREEMPTIVE_OS_LOOKUPACCOUNTSID
January 12, 2011 at 12:19 am
June 26, 2012 at 11:02 am
I have problems with that kind of waits
PREEMPTIVE_OS_AUTHENTICATIONOPS
wait_typewaiting_tasks_countwait_time_msmax_wait_time_mssignal_wait_time_ms
PREEMPTIVE_OS_AUTHENTICATIONOPS146477045791693275300
someone to give me a clue pleaaaaase????
June 26, 2012 at 3:58 pm
June 26, 2012 at 4:35 pm
Yes! I already had read it. And makes some sense; but even with all consoles closed I continue to see this wait increasing.... =(
June 27, 2012 at 1:33 am
Have you checked that the DNS/AD settings are correct.
I also found an issue when the SQL server have an old DNS server as the primary.
June 27, 2012 at 9:05 am
Yes i have checked and everything looks fine... =(
But then I can i assume that this kid of problems could be caused by the infraestructure or for the environment authentication (DNS, Active Directory, WINS, DHCP etc. etc.) ??????
I DO NOT UNDERSTAND WHY MICROSOFT IS NOT DOCUMENTED THIS.
October 29, 2012 at 5:30 am
Hi
Looking at the wait type and what's involved it seems like there will ALWAYS be a wait whenever you invoke a SID lookup, even if that wait is only 1 millisecond or less. The key here is whether or not the wait type is having an impact. if you divide the Wait_time_ms by the Waiting_tasks_count you should see the average ms/wait and if the post you made earlier is accurate that means that the waits are averaging at less than 1 ms. I don't think you need to worry about this.
If it is troubling you, you could setup a query that looks at the wait stats regularly (Daily, hourly or less or more frequently) and notifies you when the wait type goes over X ms (up to you to decide what is bad for your environment, I would say averages of 5ms or higher are probably bad). Remember to flush your stats regularly for accurate results though as they are cumulative.
Hope this helps,
Richard
May 10, 2013 at 1:07 am
It might be related to some sort of OS memory leak triggered by some random event, rebooting the server often resolves and stablizes it (based on experience rather than insider knowledge). I know of a server where an instance restart will trigger ever increasing PREEMPTIVE_OS_AUTHENTICATIONOPS wait type times, a server reboot stablizes it. When it reaches between 12-15% the impact becomes noticeable.
May 10, 2013 at 1:17 am
PREEMPTIVE_OS_AUTHENTICATIONOPS could indicate problems talking to a domain controller - not personally experienced this though.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply