Multiple Hierarchy Best Practice Quesiton

[samonsey]

I have I dimension which has a name and a code for each record. I am wondering if the best practice would be to have the code as a child of the name, or create separate hierarchies for the code and the name, since there is not a one to many relationship, but a one to one relationship between the code and the name.

Thanks,

Asa Monsey
samonsey@houston.rr.com
Tek Systems, Inc. Consultant
Visual Basic / SQL Server

 

[MDXer]

Will people be reporting based upon the code as well as the name? or Do they need to see the Name and the code together?

Best Approach is to determine what the reporting needs are and then design based upon those needs. If people want to report based upon codes and names seperately then a Multiple Hierarchy would make some sense. If the need is to see a name and it code together you could do this a number of ways. It really boils down to how users need to do their reporting.

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck