Database Reference
In-Depth Information
Figure 10-7.
A new user-defined attribute hierarchy
Each dimension can have many hierarchies, and the implied individual hierarchy exists even after you
create your own user-defined attribute hierarchies. In our example, we have three attributes and have added
a user-defined hierarchy, so we now have four hierarchies total. Figure
10-8
is a conceptual example of this
concept.
Figure 10-8.
The DimAuthors dimension including the new user-defined attribute hierarchy
The attributes AuthorID, Author, and AuthorState still form their own hierarchical parent-child relationship
with the All attribute. Microsoft calls these
attribute hierarchies
in contrast to the term
user hierarchies
.
Microsoft recommends hiding attribute hierarchies if you will not use them independently in your reporting
applications. They can be hidden by setting the AttributeHierarchyVisible property to False, as shown in Figure
10-9
.
