SQL Server Extended Events has a highly scalable and highly configurable architecture that allows users to collect as much or as little information as is necessary to troubleshoot or identify a performance problem.
You can find more information about Extended Events on the web at SQL Server Extended Events.
Extended Events is a light weight performance monitoring system that uses very few performance resources. Extended Events provides two graphical user interfaces (New Session Wizard and New Session) to create, modify, display, and analyze your session data.
SQL Server Extended Events (Extended Events) builds on existing concepts, such as an event or an event consumer, uses concepts from Event Tracing for Windows, and introduces new concepts.
The following table describes the concepts in Extended Events.
Describes the Extended Events packages that contain objects that are used for obtaining and processing data when an Extended Events session is running.
Describes the event consumers that can receive data during an event session.
Describes the engine that implements and manages an Extended Events session.
Describes the Extended Events session.
Extended Events (Extended Events) is a general event-handling system for server systems. The Extended Events infrastructure supports the correlation of data from SQL Server, and under certain conditions, the correlation of data from the operating system and database applications. In the latter case, Extended Events output must be directed to Event Tracing for Windows (ETW) to correlate the event data with operating system or application event data.
All applications have execution points that are useful both inside and outside an application. Inside the application, asynchronous processing may be enqueued using information that is collected during the initial execution of a task. Outside the application, execution points provide monitoring utilities with information about the behavioral and performance characteristics of the monitored application.
Extended Events supports using event data outside a process. This data is typically used by:
Tracing tools, such as SQL Trace and System Monitor.
Logging tools, such as the Windows event log or the SQL Server error log.
Users administering a product or developing applications on a product.
Extended Events has the following key design aspects:
The Extended Events engine is event agnostic. This enables the engine to bind any event to any target because the engine is not constrained by event content. For more information about the Extended Events engine, see SQL Server Extended Events Engine.
Events are separated from event consumers, which are called targets in Extended Events. This means that any target can receive any event. In addition, any event that is raised can be automatically consumed by the target, which can log or provide additional event context. For more information, see SQL Server Extended Events Targets.
Events are distinct from the action to take when an event occurs. Therefore, any action can be associated with any event.
Predicates can dynamically filter when event data should be captured. This adds to the flexibility of the Extended Events infrastructure. For more information, see SQL Server Extended Events Packages.
Extended Events can synchronously generate event data (and asynchronously process that data) which provides a flexible solution for event handling. In addition, Extended Events provides the following features:
A unified approach to handling events across the server system, while enabling users to isolate specific events for troubleshooting purposes.
Integration with, and support for existing ETW tools.
A fully configurable event handling mechanism that is based on Transact-SQL.
The ability to dynamically monitor active processes, while having minimal effect on those processes.
A default system health session that runs without any noticeable performance effects. The session collects system data that you can use to help troubleshoot performance issues. For more information, see Use the system_health Session.
Using Management Studio or Transact-SQL to execute Transact-SQL Data Definition Language (DDL) statements, dynamic management views and functions, or catalog views, you can create simple or complex SQL Server Extended Events troubleshooting solutions for your SQL Server environment.
Use the Object Explorer to manage event sessions.
Describes how to create an Extended Events session.
Describes how to view and refresh target data.
Describes how to use Extended Events tools to create and manage your SQL Server Extended Events sessions.
Describes how to alter an Extended Events session.
Describes how to copy or export target data.
Describes how to modify your trace results view to customize how you want to analyze your data.
Describes how to get information about the fields associated with the events.
Describes how to find out what events are available in the registered packages.
Describes how to determine what Extended Events targets are available in the registered packages.
Describes how to view the Extended Events events and actions that are equivalent to each SQL Trace event and its associated columns.
Describes how to find the parameters you can set when you use the ADD TARGET argument in CREATE EVENT SESSION or ALTER EVENT SESSION.
Describes how to convert an existing SQL Trace script to an Extended Events session.
Describes how to determine which queries are holding the lock, the plan of the query, and the Transact-SQL stack at the time the lock was taken.
Describes how to identify the source of locks that are hindering database performance.
Describes how to use Extended Events with Event Tracing for Windows to monitor system activity.