Yesterday I asked how everyone uses Trace and Profiler… Jonathan and I have talked about creating a library of Extended Events script to help people migrate off of Profiler and Trace and that post was designed to generate some ideas about what people might find useful.
I haven’t gotten a ton of comments, but I did get a few (thank you to those have responded!), and I decided to take one of them and create a Trace and create an Extended Events session and see how long it took for each. Jonathan has mentioned before that he can create an XE session as fast as a Trace, and I’ve been thinking that I can as well so I thought I’d test it. It’s a straight-forward Trace versus Extended Events test. Want to see what’s faster? Watch the video here.
5 thoughts on “SQL Trace versus Extended Events: How long does it take to startup a trace vs. an event session?”
Seven seconds? That’s not even long enough to open Management Studio ;-). And once you’ve scripted it because you need to run it regularly, it’s no time at all. Observer overhead is lower, all those good things. Thanks for the demo, Erin.
Seven seconds? That’s not even long enough to open Management Studio ;-). And once you’ve scripted it because you need to run it regularly, it’s no time at all. Observer overhead is lower, all those good things. Thanks for the demo, Erin.
Whoop! XE Wins! The intelli-sense like searching via the GUI is pretty cool. I guess I can replace my server trace now – thanks 🙂
The searching for text in events, etc. is one of my favorite things in the UI!