How is this possible? It is a very simple query with one criterion in the WHERE clause, so if it is executing very efficiently, why are the end-users waiting 20 seconds for this query each time it executes? The answer is revealed when we review the real execution plan from a trace or by retrieving it from the dm_exec_query_plan DMO: