I designed a fact table with sales.
One dimensions contains nearly 1000 elements. I call them companies, because
they include the manufacturer
of the sales.

The other dimension consists of customer.Nearly 200000 elements are inside.

So i tried to create a query to get all customer who bought things from one
specified customer.

I wrote something like
.... non empty {descendants([Customer].[CustomerID],6)} ON ROWS...

but no chance. i'm sure there are no more than 20000 customer buying the
same thing from the same manufacturer,
but i cant get results....too big

So the only solution i know until now to build a third dimension with
manufacturer/customer hierarchy.
But this results in a long refreshing process. also this new big dimension
slows down everything...

Any idea what I could do.

thx for help in advance

the first reaction is :
does it realistic to display this information to the user?
who will read 20 000 rows on a screen?
do you really need this big list?

I recommand to focus your query. for example, what are my top 10 customers
etc...


"Bernd Schreiber" <qq (AT) web (DOT) de> a écrit dans le message de news:
eqZUlMbmEHA.4064 (AT) TK2MSFTNGP14 (DOT) phx.gbl...

its not only for screen output, but even if the result consist of 500
rows...
to get these non empty rows is not possible on this way

anyway thx 4 your comment, but it doesnt help...

or may be i am on the wrong way...



"Jéjé" <willgart (AT) BBBhotmailAAA (DOT) com> schrieb im Newsbeitrag
news:e9GhgzgmEHA.1672 (AT) TK2MSFTNGP14 (DOT) phx.gbl...

can you send your actual query?
if its not for screen output, so not for analysis... have you try to create
an SQL statement instead-of unsing your cube?

"Bernd Schreiber" <kruse08 (AT) web (DOT) de> a écrit dans le message de news:
OpC$2ajmEHA.3464 (AT) tk2msftngp13 (DOT) phx.gbl...