Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a .tdf SQL Server Profiler trace template someone wants me to run but the template is targeting SS 2008 R2. While my SSMS is 2008 R2 the server I need to trace is SS 2005. When attempting to trace the server the server type is locked (generated from the actual server) so I can't just select the template I need while it's marked as a different SS version..

Trace Template Properties window

How can I change which server type the trade template is targeting? I've tried File > Templates > Edit Templates... but there doesn't seem to be an option to change this. Is it possible to change the target server version or does the whole trace have to be made again from scratch?

share|improve this question
This is technically about the SSMS feature called "SQL Server Profiler" but we don't seem to have an explicit tag for that. – Ben Brocka Aug 29 '12 at 21:43
@MaxVernon already tried, it's a binary – Ben Brocka Aug 29 '12 at 21:49
up vote 5 down vote accepted

If you open Profiler, go to File > Templates > Import and choose your .tdf file.

You will have a new user trace template with the name [filename] (without the .tdf). Go to File > Templates > Edit and pick the trace template you imported. You should then be able to edit the server type by pulling the dropdown:

enter image description here

Then you can save the template and that should be the server type when you start a new trace using that template.

share|improve this answer
Okay, that does work. Important to note that when you pick the different server type, the template name disappears (it re-filters the templates to show you the selected server type's templates), but if you save it does edit the selected template. Disorienting, but now I know. – Ben Brocka Aug 30 '12 at 13:21
@Ben Yeah it is weird. Profiler's on the chopping block - embrace Extended Events now. – Aaron Bertrand Aug 30 '12 at 13:22
I had to use the technique recommended by @mcw0933 below. – Jeff Nov 5 '15 at 23:51

I'm using Profiler 2012, talking to 2008, 2008 R2, and 2012 databases. I had to use a slightly different workflow than in the accepted answer.

When I try to follow that workflow, to migrate a template from 2008 to 2012, the Select template name dropdown depopulates, and clicking Save or Save As prompts me to choose a template to save.

enter image description here

Instead, copy your template from the 2012 profiler, 2008 templates folder (should be %APPDATA%\Microsoft\SQL Profiler\11.0\Templates\Microsoft SQL Server\100) to the 2012 profiler, 2012 templates folder (should be %APPDATA%\Microsoft\SQL Profiler\11.0\Templates\Microsoft SQL Server\110)

Now, go to File > New Trace... and choose the copied template to perform a trace on a 2012 server. Verify the trace is running and capturing what you want.

At this point, you're pretty good - you can use the copied template to start traces. But if you want to make modifications on it, when you go to File > Templates > Edit Template... and choose Events Selection you get a prompt indicating the trace is in the wrong format:

enter image description here

To save it in the new format: start the trace running using File > New Trace... as mentioned above, then with the trace running do File > Save As > Trace Template... and choose a new name. You can now delete the originally copied template, and use the newly saved template in its place.

share|improve this answer
This technique worked for me, while the accepted answer did not. – Jeff Nov 5 '15 at 23:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.