Total execution time
The cumulative amount of time (in milliseconds) that the client spent processing while the query was executed, including the time that the client spent waiting for replies from the server as well as the time spent executing code.

Wait time on server replies
The cumulative amount of time (in milliseconds) that the client spent while it waited for the server to reply.

It would be nice to have a button or context sensitive menu option for this but I can’t find one.

Is there any way to reset -clean- the results of the client statistics pane?

Thanks for your answer

Albert

thanks
yenkay

I dont know if is the right approach, but i used it to check the size in kb of the resultset. I get the bytes sent by the server and divided by 1024. It was the first time i used it.

I’ve used this feature to compare queries that do the same thing but have different approaches. For example, I had a query that selected a MAX value and a list if items (GROUP BY) approach. The alternate query used a row_number() using the partition and ORDERing on the MAX value descending.

In this case I determined that even though the MAX/GROUP BY approach ran a bit slower, consistently, than the ROW_NUMBER approach, I opted with the GROUP BY in the production code simply because of it’s simplicitiy. In other words I was still willing to trade off a slight performance advantage for ease of support for future generations (those that have to read my stuff down the road).

Another point to add, which I know you have somewhere in your blogsite, is to make sure to flush the data and query cache between queries, unless the goal is to determine the cost of parsing, algebrizing and creating a plan.

Finally, it’s worth noting the difference between client statistic; index statistics and data statistics/sampling/histograms.

Awesome job on this site!

Dave