SQL Saturday #509 | Brisbane 2016 #509 | Brisbane 2016 Martin Catherall Moving from Profiler to Extended Events.

SQL Saturday #509 | Brisbane 2016 Martin Catherall Picture Here Senior SQL Consultant - RockSolid SQL  Data Platform MVP  PASS Regional Mentor (Asia Pacific – APAC)  SQL Saturday Organizer  South Island New Zealand  Former Leader Christchurch SQL Server User Group.  Twitter  -

SQL Saturday #509 | Brisbane 2016 Extended Events The Agenda Introduction History Extended Events Overview Targets Profiler / Trace – A Review Packages, Events, Actions Built in Event Sessions Predicates Analysis Services Summary / Questions 10

SQL Saturday #509 | Brisbane 2016 SQL 2016 Where is Management Studio?

SQL Saturday #509 | Brisbane 2016 Profiler & SQL Trace (profiler and perfmon) (Event Notifications)

SQL Saturday #509 | Brisbane 2016 Why Not Enhance Profiler? Could Impact Performance (Large Overhead) Too much data captured (filtering) Why collect data you don’t need? Not that flexible. Post event analysis. Not user friendly (SQL Trace) Covert Traces to Extended events

SQL Saturday #509 | Brisbane 2016 Extended Events - History Introduced 2008 No GUI Enhanced 2012 Profiler deprecated – Parity of events Profiler and Xevents 2014 onwards More events added. Great for troubleshooting Really great for learning. Lives in SQLOS

SQL Saturday #509 | Brisbane 2016 Extended Events - Object Model The Object Model

SQL Saturday #509 | Brisbane 2016 Targets Targets consume the session. Without then we would not see data. Files. Ring buffer (memory) Synchronous and Asynchronous Aggregate targets (simplify task) Event Pairing (begin and end) Leaves with events that have no finished ETW target. (very advanced)

SQL Saturday #509 | Brisbane 2016 Packages Packages Loaded by Modules in the Engine. Container Not a functional boundary (Mix and match) Objects from one package with objects from another Flexible

SQL Saturday #509 | Brisbane 2016 Events and Actions Events correspond to points in the code. Eg – deadlock, statement completed. Not named exactly the same as in Trace. Events have a default (basic) payload You always get that. This is versioned. Can also have optional (Customizable) elements. The Actions are added. Mix and Match

SQL Saturday #509 | Brisbane 2016 Predicates Define when an event will fire. Boolean expressions Can “short circuit” First false evaluation prevents firing Can store state Number of times they have fired. When event duration exceeds xx Filter is on Events / Actions Only executes if the event fires.

SQL Saturday #509 | Brisbane 2016 Built in Sessions System Health. Similar but not the same the default trace. Availability Groups. Writes to file in

SQL Saturday #509 | Brisbane 2016 DMV’s Active sessions. Configured sessions.

SQL Saturday #509 | Brisbane 2016 Extended Events (Analysis Services / Other Stuff)

SQL Saturday #509 | Brisbane 2016 Extended Events - Analysis Services s/2015/09/22/using-extended-events-with-sql- server-analysis-services-2016-ctp-2-3/ s/2015/09/22/using-extended-events-with-sql- server-analysis-services-2016-ctp-2-3/ MOLAP -> ROLAP (Multi-dimensional) Direct Query (Tabular)

SQL Saturday #509 | Brisbane 2016 Extended Events – From Code The Extended Events Reader (Xevent Linq Reader) SQL 2016 – It Just Runs Faster: XEvent Linq Reader.SQL 2016 – It Just Runs Faster: XEvent Linq Reader.

SQL Saturday #509 | Brisbane 2016 Extended Events – References Extended Events (SQLBlog.com) 31 days of Extended Events Pluralsight (intor xevents) Pluralsight (advanced xevents) PASS Videos Erin Stelleto Jonathan Kehayais.

SQL Saturday #509 | Brisbane 2016 Summary Xevents is Flexible. Easy to work with. Can Start / Stop easily. Is lightweight (although still some overhead) Showplan / debug AVOID debug (DBCC) in prod (use it to learn) For new functionality XEvents is necessary. Eg columnstore, in-memory. More events in XEvents

SQL Saturday #509 | Brisbane 2016 Please make sure you visit our fantastic sponsors. Questions #509 | Brisbane 2016