dbTalk Databases Forums  

Member properties in hierarchies

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Member properties in hierarchies in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Ramanand
 
Posts: n/a

Default Member properties in hierarchies - 06-01-2005 , 03:08 AM






Hi,

I have a hierarchy of levels in a dimension. Each level has the same member
property. I want to find out how the value of the member property of a parent
is set.

For e.g.: assume the dimension as Salesforce with levels: Manager and
Subordinate. Assume a member property called "target".
A manager M1 has three subs S1, S2 & S3. The dimension table rows are:
(schema: MgrName, SubName,Target)
row1: M1, S1,200
row2: M1, S2,300
row3: M1, S3,400

Now, what value will the "target" property for M1 have? [Values for "target"
for the leaf S nodes will come directly from the dimension table]

The crux of the question is: how is the value of a member property for a
parent level set? It must be derived from the children, so which child does
it choose?

In my experiments, I find that the max value of the children is given to the
parent. Is this the documented approach? Can anyone confirm this? Is there
any documentation that covers this query?

Thanks,
Ramanand

Reply With Quote
  #2  
Old   
Deepak Puri
 
Posts: n/a

Default Re: Member properties in hierarchies - 06-02-2005 , 12:31 AM






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.
...
Quote:

- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.