Hi,

I scripted a profiler trace definition to an .XMLA file, opened it and run
it to start a trace. I did it this way because i wanted to log off and keep
it running in the background.

However, i'm having real trouble putting together the XMLA to stop the
trace. I have the Trace ID etc and have been trying to run the XMLA as
follows but it keeps erroring with: "The Command element at line 7, column 24
(namespace urn:schemas-microsoft-com:xml-analysis) cannot appear under
Envelope/Body/Execute/Command."

Here's my XMLA, no giggling please!

<Command>
<Delete xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Object>
<Trace>
<ID>MicrosoftProfilerTrace1157987651</ID>
<Name>MicrosoftProfilerTrace1157987651</Name>
</Trace>
</Object>
</Delete>
</Command>

Any help would be most appreciated!
--
Kyle Henly
DBA
U.K.

Try and use SQL Server profiler for creating such trace. One of the options
in the dialog when creating a trace gives you ability to log a trace into a
file.

For stopping the trace you've created take a look again at what SQL Server
profiler doing. Please note, by default SQL Profiler trace has a filter,
filtering out all the events belong to the Profiler itself.
Remove the filter from the trace definition and then try to trace activity
another trace is doing when created and stopped. This way you should see the
right syntax for Delete command.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Kyle Henly" <KyleHenly (AT) discussions (DOT) microsoft.com> wrote

Hi Edward,

Thanks again for another cool fix!

I used Profiler (without the filter on Profiler) to trace another Profiler
trace and then stopped that trace and viewed the output. The XMLA to use was
then clear to see.

For the benefit of others, here's the XMLA to stop a trace, it's not exactly
rocket science

<Delete xmlns="http://schemas.microsoft.com/analysisservices/2003/engine"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<Object>
<TraceID>MicrosoftProfilerTrace1158155501</TraceID>
</Object>
</Delete>

Cheers...
--
Kyle Henly
DBA
U.K.


"Edward Melomed [MSFT]" wrote: