August 20, 2013 at 8:43 am
If you wish to replay events captured by the default trace can you copy the files to your local machine from the server and run them locally in profiler ?
Will the trace show what stored procs were running and who ran them ?
August 20, 2013 at 9:02 am
The files the default trace creates are normal profiler trace files. You can copy them anywhere, open in profiler, load into SQL, whatever.
It has a very limited set of events, one that does not include stored procedure execution or any DML.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 20, 2013 at 9:09 am
OK thanks Gail.
Would you recommend running server side traces to capture data in the event you need to analyse later - would you leave them running during production hours if the impact is minimal ?
August 20, 2013 at 9:23 am
Depends. Mostly on what you're trying to figure out.
To give you an idea, I have a client with a moderatly busy database that, if I trace for stored procedure completes, I get 300-400MB/hour during peak times. That's roughly (given the hours the DB is active) 3.5-4GB a day. That's a fair amount of data...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 20, 2013 at 9:52 am
I'd have to keep an eye of the size of the data it generates if i was going to go down that path then.
Thanks for the reply.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply