SQL Server: Replacing Profiler with Extended Events

Use your knowledge of Profiler and Trace to help learn how to effectively use their replacement: Extended Events. If you use Trace or Profiler in SQL Server, in any capacity, this course is relevant to you.
More
Use your knowledge of Profiler and Trace to help learn how to effectively use their replacement: Extended Events. If you use Trace or Profiler in SQL Server, in any capacity, this course is relevant to you.
More
Introduction
16m 46s
There have been three new releases of SQL Server since the introduction of Extended Events (XE) in SQL Server 2008, and DBAs and Developers alike still prefer Profiler. It's time to move on. If you've tried Extended Events and struggled, or if you've been thinking about it but just aren't sure where to begin, then this course is for you. Using your existing knowledge and experience, this course will bridge the gap between Profiler and XE through a series of demos, including how to create an Extended Events session using an existing Trace, how to create one in the UI from scratch, how to analyze the data, and what to watch out for in terms of performance. If you use Trace or Profiler in SQL Server, in any capacity, regardless of what you do as part of your day-to-day job, this course is relevant to you.

Hello, my name is Erin Stellato, and welcome to my course SQL Server: Replacing Profiler with Extended Events. I'm a SQL Server consultant with SQLskills, as well as a Microsoft Data Platform MVP, and I have been talking and writing about extended events since 2012, when I finally, truly understood how to leverage Extended Events and I wanted everyone else to see the light. Extended Events was introduced in SQL Server 2008, but as of the SQL Server 2016 release, eight years later, I find that many SQL Server professionals still prefer using Profiler and Trace when they are troubleshooting a drop performance or they want to track down poor performing queries. But here's the thing: Extended Events was written to replace Profiler and Trace, and while change is hard, the benefits that come with this new event handling system far exceed any stumbles you might encounter in the road while learning it. In this course we will use the knowledge that you already have about Profiler and Trace to understand the different components of Extended Events and how they all work together. We will walk through how to create an Extended Events session using an existing Trace, how to create one in the UI from scratch, how to analyze the data, and what to watch out for in terms of performance. If you use Trace or Profiler in SQL Server, in any capactiy, regarldess of what you do as part of your day to day job, this course is relevant to you. Experience with Profiler and Trace is expected, along with an understanding of typical troubleshooting scenarios in SQL Server. I hope you'll join me as we explore the world of Extended Events with this course, SQL Server: Replacing Profiler with Extended Events, here on Pluralsight.

Table of Contents
Introduction
16m 46s
Description
There have been three new releases of SQL Server since the introduction of Extended Events (XE) in SQL Server 2008, and DBAs and Developers alike still prefer Profiler. It's time to move on. If you've tried Extended Events and struggled, or if you've been thinking about it but just aren't sure where to begin, then this course is for you. Using your existing knowledge and experience, this course will bridge the gap between Profiler and XE through a series of demos, including how to create an Extended Events session using an existing Trace, how to create one in the UI from scratch, how to analyze the data, and what to watch out for in terms of performance. If you use Trace or Profiler in SQL Server, in any capacity, regardless of what you do as part of your day-to-day job, this course is relevant to you.
Transcript

Hello, my name is Erin Stellato, and welcome to my course SQL Server: Replacing Profiler with Extended Events. I'm a SQL Server consultant with SQLskills, as well as a Microsoft Data Platform MVP, and I have been talking and writing about extended events since 2012, when I finally, truly understood how to leverage Extended Events and I wanted everyone else to see the light. Extended Events was introduced in SQL Server 2008, but as of the SQL Server 2016 release, eight years later, I find that many SQL Server professionals still prefer using Profiler and Trace when they are troubleshooting a drop performance or they want to track down poor performing queries. But here's the thing: Extended Events was written to replace Profiler and Trace, and while change is hard, the benefits that come with this new event handling system far exceed any stumbles you might encounter in the road while learning it. In this course we will use the knowledge that you already have about Profiler and Trace to understand the different components of Extended Events and how they all work together. We will walk through how to create an Extended Events session using an existing Trace, how to create one in the UI from scratch, how to analyze the data, and what to watch out for in terms of performance. If you use Trace or Profiler in SQL Server, in any capactiy, regarldess of what you do as part of your day to day job, this course is relevant to you. Experience with Profiler and Trace is expected, along with an understanding of typical troubleshooting scenarios in SQL Server. I hope you'll join me as we explore the world of Extended Events with this course, SQL Server: Replacing Profiler with Extended Events, here on Pluralsight.

Course info
Level
Intermediate
Rating
(41)
Duration
2h 28m
Updated
1 Jul 2016
Course authors

Erin Stellato is a Principal Consultant with SQLskills and a SQL Server MVP. She has worked as a SQL Server professional since 2003 and her interests include Internals, Performance Tuning, High Availability and Disaster Recovery. Erin is an active member of the SQL Server community as a presenter and blogger.

Share course