Database Reference
In-Depth Information
When SQL Server reaches an
event point
in code, it checks for any active event sessions that consume such
an event. When such sessions exist, SQL Server collects the event data columns and, if predicates were defined, it
collects the information needed for their evaluation. If predicate evaluation succeeds and the event needs to be fired,
SQL Server collects all of the actions, passes data to synchronous targets, and buffers data for asynchronous targets.
Figure
28-1
illustrates this process.
Figure 28-1.
Extended Events life cycle
Finally, it is worth noting that Extended Events support in SQL Server 2008 is rather limited, and it does not
include all of the events that exist in SQL Trace. Moreover, Management Studio in SQL Server 2008 does not include
a UI to work with Extended Events. Fortunately, those limitations have been addressed in SQL Server 2012, where all
SQL Trace events have corresponding Extended Events, and Management Studio provides the tools to manage and
analyze Extended Events data.
■
You can download the sQL server 2008 extended events Management studio add-In developed by
Jonathan Kehayias from the
sqlskills.com
web site at
http://www.sqlskills.com/free-tools/
,
or from Codeplex.
Moreover, Jonathan wrote an excellent tutorial on extended events called “an xevent a day,” which is available at:
Note
