MS SQL Server OLAP - Drillthrough not working on geography dimension

Author

Drillthrough not working on geography dimension

2005-09-22, 9:23 am

Hi,
I have a situation where drillthrough is enabled for a cube with 14
different dimensions, one of which is a geography dimension. It
includes the levels "country", "state", "city". Drill through works
when viewing data by all other dimensions but when attempting to
drillthrough via the geography dimension on all levels it returns no
rows, just column headers (unless I drillthrough on the "All Geography
level", in which case it returns data). I have tried rebuilding the
cube (advise I have read in other threads), but end up with the same
results. Another interesting thing is, I built a test cube with only
the geography dimension and another dimension. Again the same results
as above. However when I remove the "country" level from the dimension
it works fine when drilling through on the state and city levels.
Nothing is customized on the dimension and there are no customizations
to the cube, everything is standard. Any advise would be appreciated.

Thanks,
Tom

Darren Gosbell

2005-09-26, 3:23 am

Try running SQL Profiler while doing a drillthrough operation to see
what SQL is being executed as this may give you some hints.

(assuming your data source is SQL Server)

--
Regards
Darren Gosbell [MCSD]
< dgosbell_at_yahoo_do
t_com>
Blog: http://www.geekswithblogs.net/darrengosbell

In article <1127395553.433431.87240@o13g2000cwo.googlegroups.com>,
tomkardaras@hotmail.com says...
> Hi,
> I have a situation where drillthrough is enabled for a cube with 14
> different dimensions, one of which is a geography dimension. It
> includes the levels "country", "state", "city". Drill through works
> when viewing data by all other dimensions but when attempting to
> drillthrough via the geography dimension on all levels it returns no
> rows, just column headers (unless I drillthrough on the "All Geography
> level", in which case it returns data). I have tried rebuilding the
> cube (advise I have read in other threads), but end up with the same
> results. Another interesting thing is, I built a test cube with only
> the geography dimension and another dimension. Again the same results
> as above. However when I remove the "country" level from the dimension
> it works fine when drilling through on the state and city levels.
> Nothing is customized on the dimension and there are no customizations
> to the cube, everything is standard. Any advise would be appreciated.
>
> Thanks,
> Tom
>
>

michael v

2005-09-26, 1:24 pm

And you're not selecting more than one member in the geography dimension ?

As I understand drillthrough doesn't support that

"TK" <tomkardaras@hotmail.com> wrote in message
news:1127395553.433431.87240@o13g2000cwo.googlegroups.com...
> Hi,
> I have a situation where drillthrough is enabled for a cube with 14
> different dimensions, one of which is a geography dimension. It
> includes the levels "country", "state", "city". Drill through works
> when viewing data by all other dimensions but when attempting to
> drillthrough via the geography dimension on all levels it returns no
> rows, just column headers (unless I drillthrough on the "All Geography
> level", in which case it returns data). I have tried rebuilding the
> cube (advise I have read in other threads), but end up with the same
> results. Another interesting thing is, I built a test cube with only
> the geography dimension and another dimension. Again the same results
> as above. However when I remove the "country" level from the dimension
> it works fine when drilling through on the state and city levels.
> Nothing is customized on the dimension and there are no customizations
> to the cube, everything is standard. Any advise would be appreciated.
>
> Thanks,
> Tom
>

2005-09-30, 8:24 pm

Thanks for the responses. I couldn't run tracer (unfortunately I am
using Oracle as the source). I figured out the problem was that
analysis services seems to right justify the field when querying the
source data. The coutry field was defined as Char(4) in the database. I
simply added the TRIM() funtion to the member name and member key
columns and everything worked fine.
One of those easy fixes that you can't easily see.
Again, I appreciate the responses.

Sponsored Links