|
|
|
|
|
|
|
|
|
Saving a Trace Definition in SQL Server Profiler
Most of use Profiler interactively, but there are times when we need to run a server side trace without the UI. Should you create the script by hand? Is there a better way? Join Profiler export Jack Corbett for a quick walk through defining a trace in Profiler and then using that to generate a script you can run on your server.
|
|
|
|
Duration:
|
1
mins
6
secs
|
|
Skill Level:
|
100
|
|
Rating:
|
4.02
out of 5
|
|
Publish Date:
|
October 13, 2008
|
|
|
|
About the Author
|
|
I have been working with SQL Server since 1999 and have worked with versions 6.5 - 2005. I have experience in VB 6 and .NET (ASP.NET, VB.NET, C#). I currently work as a Software Developer for New Tribes Mission (www.ntm.org)
|
|
References
|
There are no downloads or recommended reading links for this video
|
|
|
Comments
|
|
Sound was low, Video really does not tell you what you can do with the saved trace script.
|
|
Jack Corbett on
1/16/2009
Jerry,
I have not experienced any sound issues. I am working on another video on what to do with the saved trace definition
|
|
Steve Roberts on
1/21/2009
Great Info! Thanks!
|
|
|
Excellent.
|
|
John H Davis on
6/24/2011
The answer to your question was wrong, both of the Yes answers were ture.
|
|
|
re: the answer to the second question:
So what happens to the Sql Server 2005 trace script settings when you try to run it on Sql Server 2000?
|
|
|
I believe there is an error in the question that asks about saving the trace as a SQL 2000 trace. The demonstrator clearly showed you can do this, when saving the trace and selecting the menu item for "SQL 2000" instead of "SQL 2005". At least this is my interpretation.
|
Must Be Logged In
|
|
|
|
|