This document provides an overview of Extended Events in SQL Server and how they can be used for tracing and troubleshooting. It discusses why Extended Events should be used over SQL Profiler, how they allow for correlation between systems using identifiers like Connection ID, and how causality tracking uses GUID, sequence and parent ID to link related events. It also includes an agenda covering these topics and demos of Extended Events in action.

1. Extended Events in Action
A Peek in the Future of Tracing
and Troubleshooting

2. About me





Senior SQL Server DBA at HP
Guest Lecturer at FMI
MCITP: SQL 2008
MCSE: Data Platform
MCSA: Windows Server 2012
 @miro_dd
2 |

3. Agenda






3 |
General Overview
SQL Server Extended Events - why use it?
What about SQL Profiler
Correlation
Causality Tracking
Use Extended Events to diagnose login failures

4. General Overview
 What is it actually?
 The ingredients
 XEvents Sessions
 Permissions
4 |

5. SQL Server Extended Events – why use it?
 Microsoft Roadmap
 Lightweight
 Graphical interface
www.flickr.com/photos/hinkelstone/
5 |

6. What about SQL Profiler
 Mapping of Event Classes to Events
 SQL Audit should be used for Security Event Class
 Easy migration
6 |

7. DEMO

8. Correlation – joining systems together
 Real Problem
 Updated TDS
 Connection ID
 Activity ID
www.flickr.com/photos/76029035@N02/
8 |

9. Causality Tracking
GUID
Sequence
Parent ID
9 |

10. DEMO

11. Key Takeaways
 Efficiency
 Lightweight*
 Usability
11 |

12. Useful Links
 Extended Events Team Blog:
 http://blogs.msdn.com/b/extended_events/
 Migrating from SQL Trace to Extended Events:
 http://blogs.msdn.com/b/extended_events/archive/20
10/12/10/migrating-from-sql-trace-to-extendedevents.aspx
 Jonathan Kehayias blog:
 http://www.sqlskills.com/blogs/jonathan/category/exte
nded-events/
12 |

13. 13 |

14. Sponsors