| DataMember |
| Written by Bryan C. Smith |
| Thursday, 27 September 2007 00:00 |
|
Take a moment to think about a typical organization. You have an employee. That employee has a supervisor who is also an employee who has a supervisor (who is also an employee) and so on and so on. (This is a classic parent-child hierarchy.) If these employees are in a sales organization, sales quota may have been assigned. Those employees that are supervisors are responsible for the sales quotas of the employees below them but may also have sales quotas of their own. Please also read part 2. |
Top Rated
- SSAS Implementation Best Practices slides in PDF format
- SSRS Report Against a SSAS Parent Hierarchy
- Handling inter-dimensional members dependency and reducing cube sparsity using reference dimensions in Analysis Services 2005
- Cube structure optimization for MDX query performance in Analysis Services 2005 SP2: Tips for Parent Child Hierarchies usage
- Handling Multiple Calendars with a M2M Scenario
- Passing MDX parameters in Reporting Services reports
- Using UserName to Control Data Access and Default Member in SSAS 2K5 (Carrie Williams)
- SSAS Tutorial: SQL Server 2005 Analysis Services Tutorial by Accelebrate

