Hi,

I'm looking for detail about the options of the attributes.
specially the cardinality & the RelationshipType.

in the adventure works sample, the customer dimension has setup all the
attributes related to the Full Name attribute as Flexible.
Why?

Some of these attributes will never changes (the Birth date for example)

but the attributes related to Commute Distance and City are setup to Rigid,
which is fine.

There is any particular reason of why the Birth Date is not rigid?

Does anyone as a sample dimension where an attribute has a cardinality of
One instead-of many?
what is the impact from a performance point of view?

Also, there is another cardinality option at the measure group / dimension
definition.
Each association between 1 dimension and 1 measure group could have a
cardinality of one or many.
Again, what is the impact of these options?

thanks for your feed back.

Jerome.

Which sample DB are you using, I have the RTM and Birthdate is Rigid (as
is gender)

Whereas commute distance is set to Flexible (which makes sense as a
customer could change address or jobs)

I am wondering if this property affects the aggregations on the
attributes. I know in AS2k that changing dimensions had what were
referred to as flexible aggregations (they were calculated at runtime,
but could be stored in cache) while non-changing dimensions had rigid
aggregations and their aggregations could be persisted to disk.

This is just a guess on my part, but if I am right, this would make it a
VERY important setting for performance optimizations.

Hopefully someone else has some more detailed info on this.

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

I have the RTM too.
I'm looking the Lesson 7 sample.

Well... its not so important to understand why Adv. Works is setup like
this, but what is the impact on the performance is important.


"Darren Gosbell" <jam (AT) newsgroups (DOT) nospam> wrote