Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

James Serra's Blog

James is currently a Senior Business Intelligence Architect/Developer and has over 20 years of IT experience. James started his career as a software developer, then became a DBA 12 years ago, and for the last five years he has been working extensively with Business Intelligence using the SQL Server BI stack (SSAS, SSRS, and SSIS). James has been at times a permanent employee, consultant, contractor, and owner of his own business. All these experiences along with continuous learning has helped James to develop many successful data warehouse and BI projects. James has earned the MCITP Business Developer 2008, MCITP Database Administrator 2008, and MCITP Database Developer 2008, and has a Bachelor of Science degree in Computer Engineering. His blog is at .

SQL Server 2012 (“Denali”): Extended Events

Extended Events is a general event-handling system for performance monitoring that was introduced in SQL Server 2008.  It 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.

While there are already a number of diagnostics tools such as DBCC, SQL Trace, SQL Server Profiler, DMVs, and Perfmon, Extended Events offer several major advantages:  It is light weight, has a highly scalable and highly configurable architecture, it allows a deeper and more granular level control of tracing, and it has more events that can be captured (for example you can identify page splits and high CPU utilization by ad-hoc queries).  For further troubleshooting, you can even use Extended Events to correlate SQL Server captured event data.  For more info see Opening the SQL Server 2008 Toolbox – An Introduction to Extended Events.

In SQL Server 2012, the following features were added:

  • Ported the complete set of diagnostic events that are available in SQL Trace over to Extended Events and rounded out the set of Actions to ensure that you can produce the same data from an event session that you can using SQL Trace
  • Added a user interface.  The Extended Events user interface is built directly into SSMS and there are four primary pieces: Session list, New Session Wizard, New Session dialog, Extended Events display
  • Introduced a “management” API for Extended Events that gives you access to the “inventory” of the system (eg. lists of events, actions, etc.) as well as the ability to create, modify and delete sessions using your favorite managed language.   This API is exposed through PowerShell
  • A “reader” API that provides functionality for reading event files (XEL) and event streams coming from a running event session

Note that with SQL Server 2012, SQL Trace is deprecated.  It will be phased out over the next few released in favor of Extended Events.

More info:

SQL Server 2012 “Denali”: Extended Discussion On Usage Scenario for “Extended Events” (Part-1)

SQL Server 2012 Extended Events Update – 1- Introducing the SSMS User Interface

SQL Server 2012 Extended Events Update – 2 – The SSMS UI Part 2

What’s New for Extended Events in SQL Server Codenamed “Denali” CTP3

Introducing the Extended Events User Interface

Introducing the Extended Events Reader

Introducing the Extended Events Object Model

What’s new for Extended Events in SQL Server code-named “Denali” CTP1

From the MVPs: A GUI for Extended Events in SQL Server 2012


Leave a comment on the original post [, opens in a new window]

Loading comments...