Benefits of enabling extended events for SQL Sentry? any limitations or differences? Why isn't it the default?

* what are the benefits of enabling extended events? better performance, correct?

* any limitations or differences with legacy SQL trace? Any gotchas? 

* Why isn't it the default? 

documentation.solarwinds.com/.../enabling-extended-events.htm

  • Hey there !

    Jonathan Kehayias put together this great article that explains the differences.  There are plenty of others out there, and the same generic reasons apply to the benefits of switching to XE for SQL Sentry. Since SQL Sentry now only supports SQL Server 2014 and higher, we no longer have to worry about a version that doesn't have XE.  Therefore, there shouldn't be any limitations and I doubt you'll see any differences with the underlying data collection for SQL Sentry.

    Top SQL collection uses XE by default on recent versions, and I believe it has for a few years now.

    If you're looking to implement it in your deployment, I'd highly encourage you to do so.

    Feel free to reach out with any more questions on it!

    -BT

  • Getting around to this. Thanks for confirming it's the default setting, I wasn't sure based on the link here: 

    documentation.solarwinds.com/.../enabling-extended-events.htm

    I don't think we have it enabled on our server even though we're on a recent version (must have been upgraded recently) because I still see 

    select * from OpenRowset(TABLE TRCDATA, @traceid, @records) from the SQL Monitor login

    It should be pretty seamless to switch over, correct? I'll notify the DBA team!