Hello Geeks and welcome to the Day 55 of the long series of One DMV a day. In this series of blogs I will be exploring and explaining the most useful DMVs in SQL Server. As we go ahead in this series we will also talk about the usage, linking between DMVs and some scenarios where these DMVs will be helpful while you are using SQL Server. For the complete list in the series please click here.

Today I will be starting with the extended events related DMVs. The first one I would like to talk today will be sys.dm_xe_packages. This DMV lists out the packages registered with the extended events engine. I will go by the hierarchy of the extended events in SQL Server.

Sys.dm_xe_packages gives the name of the package. The description column helps you understand what this package is used for. Packages are a set of objects for which the events are exposed. When a package is dynamically loaded by a process it exposes all the objects. We can see the events and take action as required. Extended events are very light weight and replaces traces from SQL Server 2012. I quote Microsoft – “Please move away from profiler and start using Extended Events”.

So let us see what packages we have in SQL 2008, 2012 and 2014.

SQL Server 2008 and R2:

sys.dm_xe_packages 2008 and R2

SQL Server 2012:

sys.dm_xe_packages 2012

SQL Server 2014:

sys.dm_xe_packages 2014

Now we know how to see what extended events packages are available using sys.dm_xe_packages. We will further see the next set of DMVs which will help you more with choosing right events to capture. So stay tuned. Till then

Happy Learning,

Like us on FaceBook | Join the fastest growing SQL Server group on FaceBook |
Follow me on Twitter | Follow me on FaceBook