running a trace on calls to a cube

  • ive just inherited an olap analysis reporting app at work. i want to know can i query a cube, or run a trace to see what data is being called from the cube?? i ran profiler on the database the cube is in, but it doesnt show much except background sql stuff ( like connection audits and stuff) when i call data from the cube through an app.

  • If you're running Analysis Services 2000 then the logging/tracing functionality is reasonably limited.  You can check the Query Log (defaults to logging only every 10th query) *but* this log doesn't i) hold any mdx; ii) really only shows which partitions the data was returned from, and; iii) won't contain anything unless you've turned it on at the server.

    You can add the string Log FIle=myLog.txt  to your connection string and PTS (the conduit through which *all* calls to AS2000 are made) will log MDX to the file you specify.  Note that you'd have to do this to *every* client connection string on every machine - not an option in a geographically distributed or large implementation.

    There is information that can be obtained from within excel (macro's required) from the pivot cache object, things like # rows, memory used, connection string and mdx statement. But again, to see what *everyone* is doing you'd need to look at this inormation on each pivot table in each workbook for each user.

     

    Steve.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply