Is it possible to storage data on the fact table of a cube with a
parent-child dimension using non leaf memebrs of the dimension?
With ORACLE OLAP you can do something like that and so I suppose that maybe
AS do it too.
Thank you

Andrea

"Members With Data" property of parent-child dimensions:

http://msdn.microsoft.com/library/de.../en-us/dnsql2k
/html/dimmsdn.asp
Data for Nonleaf Members

With regular dimensions, there is a direct relationship between rows in
the fact table and individual dimension members. All the fields in a
dimension table row logically describe one dimension member at the
lowest level of the hierarchy. For regular dimensions, there is no data
in the fact table that relates to members at any other than the lowest
level. For parent-child dimensions, there can be data for members at any
location in the hierarchy.

Data for Members of a Parent-Child Dimension

In a parent-child dimension, all the members are of the same entity type
and can exist at any level in the hierarchy. There can be fact table
rows associated with members at any level. For example, you build a cube
that analyzes sick days and vacation days for employees. The employee
dimension is modeled using a parent-child dimension. Each fact table row
records a day taken off by an employee.

Many parent-child dimensions will have data for nonleaf members in the
fact table. If this case, you must set the Members With Data property
for the dimension when building a cube. Otherwise, cube processing
fails. By default, nonleaf members are not allowed to have associated
fact table data.

The Members With Data property has the following values:

Value Description

Leaf members only The default, leaf members only, can have associated
fact table rows.

Nonleaf data hidden Nonleaf members can have associated fact table data.
This data is not represented among the descendents of the nonleaf
members. Consequently, it might appear to end users that values
aggregate incorrectly.

Nonleaf data visible Nonleaf members can have associated fact table
data. This data is represented among the descendents of the nonleaf
members by the creation of a child for each nonleaf member.
...

- Deepak

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

Thank you very much, it works !!
There's another thing you can do with oracle with such dimensions: if you
have data in a non leaf leaf member you can specify the way the system
divides it into leaf members (I know it is possible because someone showed
it to me, but I'm not able to do that myself at now). Is there something
like that in AS?
Thank you very much

Andrea

"Deepak Puri" <deepak_puri (AT) progressive (DOT) com> ha scritto nel messaggio
news:eXyTI9EHEHA.3196 (AT) tk2msftngp13 (DOT) phx.gbl...

Not being familiar with Oracle functionality, I can't give a good answer
- should be others in the group who know.

One option, that is discussed in the Microsoft info, is "nonleaf data
hidden/visible". This controls whether the data loaded for a non-leaf
member is visible as a separate leaf child, or is included without an
associated child.


- Deepak

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