• milldyce (8/1/2012)


    A bit of a tangent, but I remember a number of queries for which response times exploded when trying to view the Execution Plan.

    Requesting an actual execution plan causes SQL Server to insert extra (invisible) operators into the executable to measure the things like actual row counts, rebinds, rewinds...and so on. The output from all this data collection is converted into XML at the end of execution and returned to the client. Understandably, all these extra operators and activity generate significant overhead.