February 27, 2013 at 3:12 am
Hi All
I kicked off a queries detail tracking(using an event file as data storage) extended events on my pre-prod environment yesterday which I ran for 5-6 hours yesterday amd then stopped it. Quite a lot of data was created(30gb) in *.xel files which was fine as it was being put on a large backup drive
Before I left work yesterday I wanted to export all this information to a table in order for me to do some tuning analysis. So I went right click->view target data then locked my computer and went home.
I came in this morning and was alarmed to find the c:\ drive out of space! Awesome 🙂
When you perform the above action SSMS creates a file on the folder C:\Users\[username]\AppData\Local\Temp\2 that is holding temporary results of what is on the view target data window.
I cant find a way to import the extended events xel files into a table in SSMS without doing the view target data thing?
Is there an easy way to do this?
Thanks
Chris
February 27, 2013 at 4:55 am
Instead of opening it up within the GUI, just run a query directly against it using sys.fn_xe_file_target_read_file
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 1, 2013 at 8:04 am
Thanks Grant. Meant to get back to this but have been swamped
It seems Im going to have to get my hands dirty with XQuery to get what I want which isnt a bad thing.
Thanks for pointing me in the right direction
Another alternative i found was that you can open up individual files
and then export those to tables. This will mimize the size of the temp file that gets created. It isnt really ideal as it wil always created the temp file on the c:\ drive
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply