Stop Profiling

Wayne Sheffield concludes his two-part series on converting a trace to use Extended Events:

This query extracts the data from XE file target. It also calculates the end date, and displays both the internal and user-friendly names for the resource_type and mode columns – the internal values are what the trace was returning.

For a quick recap: in Part 1, you learned how to convert an existing trace into an XE session, identifying the columns and stepping through the GUI for creating the XE session. In part 2 you learned how to query both the trace and XE file target outputs, and then compared the two outputs and learned that all of the data in the trace output is available in the XE output.

Read the whole thing.

Related Posts

Finding Database Growth Events

Arun Sirpal has an Extended Events session which tracks growth events on a database file: A quick post that is hopefully useful, I wanted a quick way to find the time, size of the database file size change and who caused it. I went down the extended events route using sqlserver.database_file_size_change event. By the way […]

Read More

Breakpoint Extended Event

Arun Sirpal is a dangerous man of mystery and danger, but mostly danger: I did a dangerous thing, and I want to make sure that YOU DO NOT do the same. I was creating a couple of extended events sessions and was playing around with some actions. I ended up with the following code where I […]

Read More

Leave a Reply

Your email address will not be published. Required fields are marked *

Categories

May 2017
MTWTFSS
« Apr  
1234567
891011121314
15161718192021
22232425262728
293031