The intent of Member Properties is that each member have a uniquely
defined value for each property. So, though it may be interesting to
know what happens when properties are not uniquely defined, what is the
actual problem to be solved?
http://msdn.microsoft.com/library/de.../en-us/olapdma
d/agenhancingdims_3okz.asp
Quote:
|
Creating Member Properties
|
...
Before you create a member property in a dimension level with a source
column containing nonunique values, you must ensure that each member in
the level can have only one value for each member property. Otherwise,
member property values will be incomplete and misleading because only
one value can be displayed for each member. For example, values in the
source column of the Salesperson level are not unique. Each Salesperson
can have only one Manager, so Manager is a valid member property in the
Salesperson level. However, a Salesperson can work in multiple Regions,
so Region is not a valid member property. If Region were defined as a
member property, it would display only one Region to end users, even for
Salespersons who work in multiple Regions.
...
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.developersdex.com ***