| title | SQL Server Extended Events Targets | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 06/13/2017 | ||
| ms.prod | sql-server-2014 | ||
| ms.reviewer | |||
| ms.technology | database-engine | ||
| ms.topic | conceptual | ||
| helpviewer_keywords |
|
||
| ms.assetid | e281684c-40d1-4cf9-a0d4-7ea1ecffa384 | ||
| author | mashamsft | ||
| ms.author | mathoma | ||
| manager | craigg |
[!INCLUDEssNoVersion] Extended Events targets are event consumers. Targets can write to a file, store event data in a memory buffer, or aggregate event data. Targets can process data synchronously or asynchronously.
The Extended Events design ensures that targets are guaranteed to receive events once and only once per session.
Extended Events provide the following targets that you can use for an Extended Events session:
-
Counts all specified events that occur during an Extended Events session. Use to obtain information about workload characteristics without adding the overhead of full event collection. This is a synchronous target.
-
Use to write event session output from complete memory buffers to disk. This is an asynchronous target.
-
Many kinds of events occur in pairs, such as lock acquires and lock releases. Use to determine when a specified paired event does not occur in a matched set. This is an asynchronous target.
-
Event Tracing for Windows (ETW)
Use to correlate [!INCLUDEssNoVersion] events with Windows operating system or application event data. This is a synchronous target.
-
Use to count the number of times that a specified event occurs, based on a specified event column or action. This is an asynchronous target.
-
Use to hold the event data in memory on a first-in first-out (FIFO) basis, or on a per-event FIFO basis. This is an asynchronous target.
Extended Events
SQL Server Extended Events Packages
SQL Server Extended Events Sessions
SQL Server Extended Events Engine