Team blog of the Microsoft EMEA support team for Analysis Services
A short post to illustrate a pattern which I only recently clarified. Ever wondered why your "time" columns in a SSAS profiler trace had all .000 values for milliseconds (therefore giving you only a precision level of a second) ?
Well this seems to happen when it is the Profiler tool that collects the trace, as opposed as when the SSAS service process does it (hmm do we need another post to clarify those flows ? let me know :) )
This comes from testing, I didn't fully investigate the reasons why, maybe later..
Note that this is completely separate from the microsecond precision feature of profiler for SQL Server Core DBMS engine.
Hope that helps :)