I'm running the "SQL Server Analysis Services Tutorial" (see http://msdn.microsoft.com/en-us/library/ms170208.aspx
), using Visual Studio 2008 against the AdventureWorks database in SQL Server 2008. I'm finding the "Attribute Relation" tab within the cube design to be extremely baffling and frustrating. I would appreciate a salient description of the connection between creating a hierarchy and setting Attribute Relationships. Specifically, I am getting warning messages that I do not understand: "Attribute relationships do not exist between one or more levels of this hierarchy. This may result in decreased query performance."; "Avoid visible attribute hierarchies for attributes used as levels in user-defined hierarchies."; and "Set at least one of the attribute types to match the 'Time' dimension type." I've attempted to change the Attribute Relationships so they match the levels hierarchy (Year/Semester/Quarter/Mon
th/Date), which results in errors and an application that won't deploy.
Since an application that deploys with warnings is a far lesser evil than one that won't deploy, I've chosen not to perform those procedures that have me resetting Attribute Relationships. I've tried resolving the question using help screens, but I get definitions for people who already know what they're doing: without concrete examples, these descriptions are worthless. I would really appreciate a plain-English description of "Dimension Usage", perhaps including a link to a simple example of an Analysis service that deploys with no warning messages. Im just learning about Analysis Services, and the "Attribute Relationships" feature is proving to be insurmountable stumbling block.
Many thanks, ~Peter Ferber