Extended Events - Pro SQL Server Internals - page 550

Figure 28-12. wait_types map keys values
Targets
When all event data is collected and the event is fired, it goes to the targets , which allows you to store and retain raw
event data or perform some data analysis and aggregation.
Similar to packages, some targets are private and cannot be used in an Extended Events sessions definition. You
can examine the list of public targets by using the code shown in Listing 28-9.
Listing 28-9. Examining targets
select
xp.name as [Package]
,xo.name as [Action]
,xo.Description
,xo.capabilities_desc as [Capabilities]
from
sys.dm_xe_packages xp join sys.dm_xe_objects xo on
xp.guid = xo.package_guid
where
(xp.capabilities is null or xp.capabilities & 1 = 0) and
(xo.capabilities is null or xo.capabilities & 1 = 0) and
xo.object_type = 'target'
order by
xp.name, xo.name
The set of available targets is pretty much the same in different versions of SQL Server. Target names, however,
are different between SQL Server 2008/2008R2 and SQL Server 2012/2014. Figures 28-13 and 28-14 show the list of
targets in SQL Server 2008/2008R2 and SQL Server 2012/2014 respectively.