With Analysis Services 2005 (2008) you can collect traces without using gui this feature is known as Server Side Tracing.
In this article we’ll talk about how to achieve Server Side Tracing.
How to create a Server Side Trace
- Open SQL Server profiler connect to Analysis Services and in an Event Selection define the SSAS Events.
- Next script the trace by going to "File – Export – Script Trace Definition – For Analysis Services 2005 (AS 2005 and 2008 in case of 2008)".
- Open the Script file in Notepad and cut and copy the Events and Filter Elements to below mentioned script.
<!–Copy this Script file in Notepad and Replace Events and Filters Elements with the elements which you had generated from Trace Definition file—>
Open Management Studio on Server or any Client box connect to Analysis Services then go to file –> New XMLA Command –> Copy this Script and Execute it, this will initiate Trace on Server.
How to Find out whether Script is Running
<!–This script will give you a list off all running traces—>
How to Drop the Trace which you had created
<Delete xmlns=http://schemas.microsoft.com/analysisservices/2003/engine xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<TraceID>DBA Performance Trace</TraceID>
When you generate a trace definition using Profiler Trace it excludes LogFileName, LogSize etc, that is why I had suggested to use script which I had created.
Secondly, you need to define the stop time or you can drop the trace by giving above mentioned command (this will only stop the trace but will not physically drop the file).
This trace script file is amended from an example given in SSAS Processing Best Practices
SE, Microsoft SQL Server Analysis Services