I'm fairly new to DPA. Wait time implies time waiting for something. Depending on the perspective it could mean waiting on blocked resources or waiting on query to complete.
Thanks
The short answer is yes and yes. Actually, when you look at DPA, the cpu/memory activity represents a lack of wait within the database engine (the query is executing).
The reason we include it in the wait analysis is that we're taking an end-user perspective. They don't care what's happening under the hood, they only care how long it takes to get their results (they are waiting). Their query could be executing (cpu/memory activity), blocked (LCK% or enq% wait), making an OS call (preemptive_OS%), etc. If the thread is not processing, or waiting in queue to be processed, it's suspended. cpu/memory = processing or waiting in queue to be processed. wait states = suspended activity.
Hope that helps.
Take a look at this post Database Response Time Analysis: Understanding Why The Database is Slow
Also, the product has a carousel with detailed info. On any instance, near the top right, click Learn More and then Introduction to DPA.
Let me know if you have more questions.
Yes that helps. I really wanted to know that when looking at a wait graph was I looking at how long the session was blocked or how long it took the process the query. Basically the duration value on the sql server trace log.
Thanks. I love this tool. We have already made significant improvements to our performance.
