November 15, 2017 at 3:40 am
Hi everyone,
I have en Analysis Services instance running a tabular cube, we have set up an extended event trace to be able to report on the cube-usage. Issue is from time to time I see another trace being started and I do not know the source of this trace, if I do not get rid of it myself the trace will keep running. How do I find the source of such trace?
I used following MDX to show running traces on the instance, but that does not show the source, only the startime of the trace:
SELECT * FROM $system.discover_traces
November 15, 2017 at 8:04 am
Spindrift - Wednesday, November 15, 2017 3:40 AMHi everyone,I have en Analysis Services instance running a tabular cube, we have set up an extended event trace to be able to report on the cube-usage. Issue is from time to time I see another trace being started and I do not know the source of this trace, if I do not get rid of it myself the trace will keep running. How do I find the source of such trace?
I used following MDX to show running traces on the instance, but that does not show the source, only the startime of the trace:
SELECT * FROM $system.discover_traces
Not sure what you meant by source - do you mean the user that started the trace? You don't need the source to stop the trace. You can delete the trace using the traceid with something like:
<Delete xmlns="http://schemas.microsoft.com/analysisservices/2003/engine" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<Object>
<TraceID>YourTraceIDFrom$system.discover_traces</TraceID>
</Object>
</Delete>
Sue
November 15, 2017 at 10:09 am
Hi Sue_H,
Sorry if I was unclear, I am actually trying to chase down the source of the trace, which user / process started the trace and from where.
I have deleted the trace many times, but within a couple of days it is back, and I have yet to find out where the trace is coming from...
November 15, 2017 at 10:48 am
Spindrift - Wednesday, November 15, 2017 10:09 AMHi Sue_H,Sorry if I was unclear, I am actually trying to chase down the source of the trace, which user / process started the trace and from where.
I have deleted the trace many times, but within a couple of days it is back, and I have yet to find out where the trace is coming from...
You would need to run a trace to capture that information. If it's not the FlightRecorder trace (one you probably should leave alone) then you can pick up traces in a Profiler trace capturing the Notification event and ObjectCreate subclass. And then the objectname column in the trace will match the TraceID/TraceName when you query $system.discover_traces
You can capture the user but not the application. The column for application can be selected but won't populate with anything.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply