We had a sudden disk usage explosion this morning and the SQL monitor has no useful query information. I decided to check on any potential traces that could have captured something.
SELECT * FROM :: fn_trace_getinfo(default)
gives me
traceid property value
------- ------- ------
1 1 1
1 2 NULL
1 3 5
1 4 NULL
1 5 1
Property #2 should be the file name to which the trace is going but, as you can tell, it's NULL
.
It's running, and just to confirm, I did this which confirms that the trace is running, has no stop condition, grows max file size of 5MB (default).
Is there a way to determine the destination of this trace, or is it a known location and my Google-FU is broken?
Best Answer
NULL
means it's using the rowset provider for trace I/O. See for reference the below article:Server-Side Tracing and Collection (section "Querying Server-Side Trace Metadata")
For details on
rowset provider
see for example:SQL Trace Architecture and Terminology