Extended Event Query Post Execution Showplan in SQL Server

Play Extended Event Query Post Execution Showplan in SQL Server

The Discussion

  • User profile image
    This is the problem with non-real world workloads and incorrect conclusions about the events overall performance impact. For this specific workload the impact may only be 2ms per statement, but the execution plan is also incredibly simple and small compared to a real world workload plan which can take much longer for generation and increases the overhead of this event. Additionally the ring_buffer is the absolute worst target to use for events that generate lots of data like the showplanxml, since the DMV can only output a 4MB XML document, and it is highly likely that the target will hold events that you have absolutely no way to access if they don't fit in the 4MB of XML serialized out of the DMV.

Add Your 2 Cents