The key error logging mechanisms for Analysis Services are:
- Keep track of the data stored in msmdsrv.log . You will need to copy the log before it is overwritten.
- If you use Analysis Services 2005, 2008 or 2008 R2, you can generate your own trace events, as indicated in the System-wide trace file section of the article "Recommendations for Processing Analytical Services" at: http://technet.microsoft.com/en-us /library/cc966525.aspx#EBAA
- If you are using SQL Server 2012, you can use the XEvents function as described in the SSAS documentation. Use SQL Server Advanced Events (XEvents) to Monitor Analysis Services: http://msdn.microsoft.com/en-us/library/gg492139.aspx
Another approach is to use running SQL Server Profiler in the background so that you can record all events. But it will be similar to option # 2.
Also note that option # 3 (using XEvents) has the least impact on your Analysis Services server in terms of resource utilization.
source share