You have to optimize the indexing of the underlying
relational tables on which the cube is built, because
drillthrough issues a SQL query to the data source. You
can capture this query and use it to optimize indexing.
But common-sense indexing will often improve drill-through
performance dramatically. For example, ensure that the
cube fact table is indexed on columns that are specified
in the drill-through query (date is a common case).


have drilthrough enabled. With that cube, I am able to
browse the data and drillthrough to the source.
When it doesn't work, I get the error: "Unable to drill
through. The operation requested failed due to timeout."
I have read high and low to find out what is wrong. The
problem is that Analysis Service allows 15 secodns to
connect to the query. With service pack 1 installed, the
time limit goes up to 30 seconds. This is a know
limitation to Analysis Server. The solution to problem is
to optimize analysis server.

How can you capture the query ? With As ?

\Michael Vardinghus

"Deepak" <anonymous (AT) discussions (DOT) microsoft.com> skrev i en meddelelse
news:8f8d01c43319$f5551790$a501280a (AT) phx (DOT) gbl...

You could use the capture/trace capabilities of the data source against
which AS runs the drill-through query. For example, I have used SQL
Profiler to capture the query to a SQL Server data source (only twist is
that the query string was passed as a param in a sys stored proc call):

From SQL Server BOL

SQL Profiler is a graphical tool that allows system administrators to
monitor events in an instance of Microsoft® SQL Server™. You can capture
and save data about each event to a file or SQL Server table to analyze
later. For example, you can monitor a production environment to see
which stored procedures are hampering performance by executing too
slowly.
...

- Deepak

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!