Since I started actively participating in SQL community, I found it is very common that people will approach to seek help on their SQL related issues. I do love to help people because it is always a win and win situation for both of us.

Recently, I had a phone conversation with one of the community members (CM) on one of the SQL issues. At some point, I asked him (CM) to capture some data for troubleshooting purpose. Below is what we discussed over the phone;

• ME: Can use the extended event to capture the advised data?
• CM: Can I use SQL Trace instead extended event (xEvents)?
• ME: Why SQL Trace… why not extended event?
• CM: I am very used to with SQL Trace. I find difficulties with the extended event because I don’t know what columns I need to select in the Extended Events. The column names are different in xEvents compare to SQL Trace.
• ME: Agreed the fact that xEvent names don’t match up to SQL Trace event names

The challenge which he faced that motivates me to write this blog. In this blog, you will explore all the SQL Trace columns are mapped to which extended events columns. You can run the below code to view the SQL Trace event, and its associated columns are mapped to which extended events and their associated columns.

SELECT DISTINCT
        tc.name 'Trace Category Name',
        te.name 'Trace Event Name', 
        em.package_name AS 'xEvent Package Name', 
        em.xe_event_name AS 'xEvent Name'  
FROM sys.trace_events te
INNER JOIN sys.trace_categories tc ON te.category_id = tc.category_id
LEFT OUTER JOIN sys.trace_xe_event_map em ON te.trace_event_id = em.trace_event_id

Below is the output of the script;

Thanks!

The post Mapping SQL Trace to Extended Events appeared first on .