Converting Trace to Extended Events

Question

Converting Trace to Extended Events

Steve Jones - SSC Editor

SSC Guru

Points: 734449
More actions
June 20, 2018 at 10:13 pm

#73760

Comments posted to this topic are about the item Converting Trace to Extended Events

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

ctrlb Old Hand Points: 386 More actions · Answer 1

This can also be done in PowerShell. I wrapped a slightly modified version of Jonathan's procedure in ConvertTo-DbaXESession and added it to dbatools

Here's how to convert the trace with id of 2 on two different servers, convert them to XE sessions named "Long Running Queries" then start them immediately

Get-DbaTrace -SqlInstance sql2017, sql2012 | Where Id -eq 2 | ConvertTo-DbaXESession -Name 'Long Running Queries' | Start-DbaXESession

Chrissy
Founder, dbatools.io

Steve Jones - SSC Editor SSC Guru Points: 734449 More actions · Answer 2

Ah, should have added that to the article. I'll put a note at the end.

S. Kusen SSChampion Points: 10936 More actions · Answer 3

Good write-up, Steve. I like that once you have the session defined the way you like, you can script it out, and I think it might actually be easier than profiler to set up a quick trace. For example, if I'm searching for text showing up in a query, or specific stored proc, I can have that script saved and do a find/replace anywhere the sql_text is set on an action and fire up the session. Thanks for sharing!

alen teplitsky SSC-Dedicated Points: 30014 More actions · Answer 4

Personally I like Extended Events better than profiler. But my biggest complaint is not setting up the session, but changing it. It was easier on profiler than editing the query and getting the parentheses and commas right in XE

Steve Jones - SSC Editor SSC Guru Points: 734449 More actions · Answer 5

alen teplitsky - Thursday, June 21, 2018 2:54 PM
Personally I like Extended Events better than profiler. But my biggest complaint is not setting up the session, but changing it. It was easier on profiler than editing the query and getting the parentheses and commas right in XE

Not using the UI?

Steve Jones - SSC Editor SSC Guru Points: 734449 More actions · Answer 6

S. Kusen - Thursday, June 21, 2018 7:02 AM
Good write-up, Steve. I like that once you have the session defined the way you like, you can script it out, and I think it might actually be easier than profiler to set up a quick trace. For example, if I'm searching for text showing up in a query, or specific stored proc, I can have that script saved and do a find/replace anywhere the sql_text is set on an action and fire up the session. Thanks for sharing!

The same thing works in XE, which also then could have a much lower performance impact. I'd save out the ALTER script and then do the search/replace in the predicate if needed.