1 DBA's Professional Blog
In the world of profiler and SQL Trace, these actions were an actual part of the payload for the Trace event. In XE, these actions are more like add-ons. I go into further depth about what an action in XE is – here. I recommend reading that article. Due to that, I won’t be diving into great detail here about what an Action is.
Templates are a powerful tool in so many trades and crafts. From decals and stickers all the way up to the largest cruise ships in the world, templates can be found everywhere in just about everything that do.
In SQL Server, templates are readily available for your use in so many different ways that I am sure we are unaware of most of them.
Several years back, when Extended Events was brand new, it was downright painful to try and convert the classic Profiler or Server Side trace to something meaningful and useful within Extended Events.
Considering this “feature” for everything that is SQL Server related, does this mean that all Extended Events related messages are accessible in sys.messages?
Some view the permissions for Extended Events as a limitation. I see the required permissions as an appropriate set and recommend all to work with XE and permissions to provide higher efficiency to their environment.
If an application vendor has something built into their code to perform index maintenance, unbeknownst to you, that is a near-worst case scenario.