Extended Events II

Extended Events I

Managing SQL Server Extended Events in Management Studio

We’ve all heard about Extended Events and how they can help troubleshoot SQL Server performance, connectivity, and locking problems, but they seem so difficult to implement using T-SQL. Isn’t there a better way to implement SQL Server Extended Events?

Using Extended Events to troubleshoot SQL Server issues

As a DBA, you'll encounter elusive performance, connectivity and locking problems that you'll need to troubleshoot. There are many tools that you can use such as Profiler. In addition to these tools, SQL Server 2008 offers extended events ("XEvents"), which you can use as a powerful tracing system. By default, the "system_health" extended events session is always on, and can provide you help to locate the source of trouble much faster.

Getting Started with Extended Events in SQL Server 2008

In a previous tip, we did an overview of Extended Events and the different components that make up Extended Events. Now that you know what Extended Events offers, how do you use it to help troubleshoot performance issues? In this tip we take a step by step look at how to implement and use Extended Events.

An Overview of Extended Events in SQL Server 2008

In this tip we look at Extended Events for SQL Server 2008 and how they are different from earlier tracing and troubleshooting methods.

Extended Events

Extended Events