Why don't try perspective for your first requirement to show different
product for different user.
I don't think No.2 is a real issue, for fact records are linked to their
product in the star schema tables.
[quoted text, click to view] "Statsman" wrote:
> I have a parent-child product dimension.
> It is parent-child because it is unbalanced - some products have more
> levels than others.
> This dimension has the product members for the entire Group.
> However, because different products have different relevant dimensions
> I have a number of cubes - i.e. I don't want to put all measures & all
> dimensions of all products into just one cube.
> If I were to use this product dimension in all cubes I have two
> problems:
> 1. The end user sees numerous 'irrelevant' product members when
> exploring the dimension
> 2. More seriously, because the seperate cubes will only have facts for
> the appropriate products the aggregation up to 'All' (Group) will be
> misleading.
>
> It would seem that I should have a centrally maintained product table &
>
> from this create a number of subset product dimensions.
>
>
> Is this the best approach?
>
>
> Many thanks.
>