SSAS Articles 
Design Attribute relationships explained (by Richard Tkachuk)
Design Attribute relationships explained (by Richard Tkachuk)
| Attribute relationships explained (by Richard Tkachuk) |
| Written by Richard Tkachuk |
| Tuesday, 01 May 2007 15:22 |
|
The purpose of this document is to define how attribute relationships affect calculations. Attribute relationships have other impacts such as query performance that are only briefly mentioned here. In Analysis Services 2005, Attribute relationships define functional dependencies between attributes. In other words, if A has a related attribute B, written A è B, there is one member in B for every member in A, and many members in A for a given member in B. More specifically, given an attribute relationship City è State, if the current city is Seattle, then we know the State must be Washington. |
Latest Author Articles
- MDX Performance Hits - v2
- Handling Begin and End Times in SQL Server Analysis Services 2008
- IIF Function Query Hints in SQL Server Analysis Services 2008
- Richard Tkachuk discusses the SQL CAT team, working with Analysis Services
- Querying Dimension Members In Analysis Services
Top Rated
- SSAS Implementation Best Practices slides in PDF format
- SSRS Report Against a SSAS Parent Hierarchy
- Using AS Data Mining to Add Forecast Values to a Cube
- 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)
