I believe SQL Doctor uses server side Traces to get information (at least I think it does).
Is it possibly that the size of information it is trying to collect can cause the trace file to grow and “crash”.
I have 1 TB of data across server databases on a SQL 2012 Enterprise box. Every time I use SQL Doctor on it, I get a —
Trace ID ‘4’ was stopped because of an error. Cause: Stopping the trace because the current trace file is full and the rollover option is not specified.. Restart the trace after correcting the problem
Can the code be re-written to accommodate for growth and multiple files on this trace?
You’re right. During some portions of analysis we do run a trace on the workload. That error message would suggest that we don’t have trace rollover set for these traces, though, so they could fill up and only show us a narrow portion of the overall workload.
I’ll take this in to Support for further investigation. If we make a change in the code that accommodates multiple rollover files, we can update you when a release that includes that comes out.
The nice thing is it doesn’t crash the application, it just doesn’t give a “complete” picture of the server.
Thank you sir!
Has there been any movement on this trace file issue?
If the error occurs, what does that mean for the data collected and its analysis? Does it still give the complete picture?
Thanks in advance…
yup, still waiting on a possible solution for this problem.
I guess this “functional” request is not high on the priority list? That’s a shame, because as it is pretty much useless with large databases/servers.
Powered by IDERA