November 23, 2008 at 8:45 pm
Hi all,
As I am new to MS SQL, I am not very familiar with it and hope that someone out there can help me
Currently I am running Profiler90 via profiler GUI and outputting the filtered results into another table of another database. However, it is so inconvenient that I need to re-create the trace of the profiler whenever the database is reset or rebooted for maintenance.
I have done some research that profiler can be started up via command line but only output to a file and not a table.
Has someone got any idea on how to create the profiler via command line with outputting the results to the table?
Your help is greatly appreciated.:)
JL
November 24, 2008 at 11:38 am
Hi,
You are right, there is now way to start the trace from script and direct the output to a table. However, you can direct the output to a trace file and then load the trace file created into a table by using the fn_trace_gettable system function.
So export the tracedefinition you have defined in Profiler (File/Export) and then run the script to create the trace on the server (first change filename etc.). Use sp_trace_setstatus to start the trace.
If you want to have this trace to start automatically when the server starts/after reboot, create a procedure that runs sp_trace_setstatus and then run sp_procoption to make that new procedure a startup procedure.
Oh, btw, you can create a Profiler template to avoid having to redefine your traces in Profiler.
HTH
/Elisabeth
elisabeth@sqlserverland.com
MCITP | MCT
http://sqlblog.com/blogs/elisabeth_redei/
http://linkedin.com/in/elisabethredei
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy