Re: Drillthrough problem

From: Dave Wickert [MSFT] (dwickert_at_online.microsoft.com)
Date: 03/11/04 

Date: Wed, 10 Mar 2004 20:15:40 -0500

Is "bananas" a technical term? :-)

BTW: another thing about optimize schema is that it might also mean that
errors start occuring in your data when you process the cube/partition. This
is caused by the fact that an unoptimized schema has an inner join with the
dimension table and -- as we all know -- inner joins eliminate data with no
matching fields. So if you have records in your fact table that point to
non-existent dimension members, then in the processing of an unoptimized
schema -- they just disappear before AS even sees them. If you then optimize
the schema, you might start getting "unknown dimension members" errors
because the inner join was eliminated. This can sometimes cause DBAs to
freak out when it first shows up. Errors just start appearing where there
were none before -- the truth is that they *WERE* there before but the
unoptimized schema just filtered them out. Just FYI -- to save from
scrambling around a second time . . . 

-- 
Dave Wickert [MS]
dwickert@online.microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Vardinghus" <mivar@wmdata.dk> wrote in message
news:OEX3u4tBEHA.2888@TK2MSFTNGP09.phx.gbl...
> Figured it out myself.
>
> When using the Optimize schema feature in as the member key column of my
> dimension table was changed to the member key column in the fact table -
> however - didn't get a warning saying drillthrough would go bananas using
> this feature...
>
> The name of the feature didn't give me any warning....:)
>
> \Michael V.
>
> MichaelV <anonymous@discussions.microsoft.com> wrote in message
> news:846BCF81-77EA-475D-ADED-1FFD2FC9FA31@microsoft.com...
> > Hi All
> >
> > I have enabled drillthrough on the fact-table and one corresponding
> dimension table.
> >
> > When I try to drill a specifik dimension member in the cube browser it
> returns an  odd result - it actually repeats a record from the fact table
> endlessly with all the dimension values from the dimenson table - despite
> the fact that i had chosen af specifik dimension value.
> >
> > When performing an sql-sentence in my relationel database joining these
> two tables it returns 289 rows in 0 seconds.
> >
> > What is wrong with my as-environment ?
> >
> > Michael Vardinghus
>
>

Relevant Pages