Ten features you had in Profiler that are missing in Extended Events

Oooooops!

I exchanged some emails about my post with Jonathan Kehayias and looks like I was wrong on many of the points I made.

I don’t want to keep misleading information around and I definitely need to fix my wrong assumptions.

Unfortunately, I don’t have the time to correct it immediately and I’m afraid it will have to remain like this for a while.

Sorry for the inconvenience, I promise I will try to fix it in the next few days.

Archived WordPress comments (1)

Historical comments from the original site; this archive is read-only.

replicationguru October 29, 2013 at 09:55
I agree. As per my opinion, XE UI and features that SQL Server offers are still not enough when compared with the flexibility of SQL Profiler.
In more than one recent training session, it was observed by the students that the UI still look as "in progress" (and this is probably the case ).

To overcome the SQL Profiler overload against production servers,I think a pretty "old style" solution still appears a fasible option:
generate the trace file script using profiler, and run it against the production server. Load the TRC file later on with profiler in offline mode.