Avoid creating hierarchies where attribute relationships do not exist between one or more levels
This rule analyzes each user hierarchy to determine whether levels exist that are not related to each other through attribute relationships.
Best Practices Recommendations
For best performance, you should typically avoid creating hierarchies where attribute relationships do not exist between one or more levels. Having attribute relationships between every level in a hierarchy makes the hierarchy strong and enables significant server optimizations.
For More Information
For more information about how to configure attributes and user hierarchies, see Defining and Configuring a User-Defined Hierarchy and Specifying Attribute Relationships Between Attributes in a User-Defined Hierarchy in SQL Server Books Online.
For more information about performance issues related to attributes and user hierarchies, see the section, "Effectively using hierarchies," in the SQL Server 2005 Analysis Services Performance Guide.