Stats Time Versus Plan Operator Time

Erik Darling explains why SET STATISTICS TIME ON can give you different timing results from what the execution plan states:

Here are the relevant details:

SQL Server Execution Times:
CPU time = 3516 ms,  elapsed time = 3273 ms.

What looks odd here is that CPU and elapsed time are near-equal, but the plan shows parallelism.

Thankfully, with operator times, the actual plan helps us out.

The query itself ran for <900ms.

The answer makes perfect sense.

Related Posts

Hidden Modals and SSIS

Jana Sattainathan knows how to make hidden modals rise to the surface in SSMS: I am not sure if run into this but I do often enough on my SSMS 17.9.1 version – suddenly, the SSMS window will not register any mouse-clicks although it will seemingly look fine. The reason is because there is a Modal […]

Read More

Execution Plan Properties

Erik Darling reminds you to check out the properties of execution plan elements: I read a lot of posts about query plans, and I rarely see people bring up the properties tab. And I get it. The F4 button is right next to the F5 button. If you hit the wrong one, you might ruin […]

Read More

Categories

July 2019
MTWTFSS
« Jun Aug »
1234567
891011121314
15161718192021
22232425262728
293031