sql 2005 profiler -- save as sql script

Question

sql 2005 profiler -- save as sql script

Uncle Boris

SSC Enthusiast

Points: 191
More actions
June 10, 2008 at 6:58 pm

#154435

Hi, maybe somebody can help with a couple of questions about SQL 2005 Profiler.
1. How do you save the trace as a SQL script. I could do this is SQL 2000 and found it easy to then open it in QA and analyse it, or run part of it or what ever, but can not see this in SQL 2005?
2. Again in SQL 2000 I could have a column called "DatabaseId" or "Database Name" so if I was profiling the entire server I could easy see what request was for what database.
I can not seem to do this in SQL 2005 . Even selecting "Show all columns" does not show it.
Any help would be appreciated.
Thanks

Viewing 4 posts - 1 through 3 (of 3 total)

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

Jack Corbett SSC Guru Points: 184394 More actions · Answer 1

Uncle Boris,

I too have struggled to find things in Profiler in 2005. I really don't like the changes MS introduced to the interface, they made it much harder to find things.

I can't answer question 1 but for question 2 you need to select show all columns, which does not add all columns to the output, but does let all the columns show in the actions pane. Then you can select the columns you do want to show by checking the boxes on the actions. You also need to show all columns in order to filter.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Uncle Boris SSC Enthusiast Points: 191 More actions · Answer 2

Thanks for the reply.

That does answer question 2.

A bit of a hassle just to get the database name for various actions but I suppose it might be easy to set it up as I want it and save it as as template.

Just have to sort out question one and all is good.

the__t Hall of Fame Points: 3260 More actions · Answer 3

From Profiler 2005, after you start the trace (seems to me you should be able to do this before clicking run, but the trace setup/properties window has control, so you can't do this until you run it)

File >> Export >> Script Trace Definition >> For SQL Server 2005...

"Got no time for the jibba jabba!"
-B.A. Baracus