SEO

Hi,

In the SSAS tutorial online Lesson 4, I am not sure what is the major
purpose of creating a "new attribute relationship" in "Dimension Structure
--> Hierarchies and levels"? I understand it is for the sorting purpose if
creating a "new attribute relationship" in the Attributes Pane. Can someone
please help me to undertand it? Thanks

Ed

Hello Ed,

If you define an attribute relationship and you define a hierarchy
including 2 attributes of the relatiionship, you could see the lowever
level attribute can aggregate properly to upper level attribute.

By default, an attribute relationship is automatically defined between the
key attribute and each non-key attribute of the dimension. Also, an
attribute relationship is automatically created between attributes have
one-to-many relationship defined in dimension tables.

However, for some natural hierarchies you have to define attribute
relationship yourselves.

Attribute relationships are an important part of dimension design. They
help the server optimize storage of data, define referential integrity
rules within the dimension, control the presence of member properties, and
determine how MDX restrictions on one hierarchy affect the values in
another hierarchy.

You could refer to the following articles for more related information:


Attribute Relationships
http://msdn2.microsoft.com/en-us/library/ms174557.aspx

OLAP Design Best Practices for Analysis Services 2005
http://www.microsoft.com/technet/pro...olapdbpssas200
5.mspx

If anything is unclear or you have furhter questions, please feel free to
let's know.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

I would like to know why there is no relationships in the Employee Department
User Defined Hierarchy in the Employee dim.

I would think on Department should have many Title and one Tile has many
Employee. Is there any reason for not having the attributes relationship
defined?

Thanks again.

""Peter Yang[MSFT]"" wrote:

> Hello Ed,
>
> If you define an attribute relationship and you define a hierarchy
> including 2 attributes of the relatiionship, you could see the lowever
> level attribute can aggregate properly to upper level attribute.
>
> By default, an attribute relationship is automatically defined between the
> key attribute and each non-key attribute of the dimension. Also, an
> attribute relationship is automatically created between attributes have
> one-to-many relationship defined in dimension tables.
>
> However, for some natural hierarchies you have to define attribute
> relationship yourselves.
>
> Attribute relationships are an important part of dimension design. They
> help the server optimize storage of data, define referential integrity
> rules within the dimension, control the presence of member properties, and
> determine how MDX restrictions on one hierarchy affect the values in
> another hierarchy.
>
> You could refer to the following articles for more related information:
>
>
> Attribute Relationships
> http://msdn2.microsoft.com/en-us/library/ms174557.aspx
>
> OLAP Design Best Practices for Analysis Services 2005
> http://www.microsoft.com/technet/pro...olapdbpssas200
> 5.mspx
>
> If anything is unclear or you have furhter questions, please feel free to
> let's know.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscripti...ult.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hello Ed,

From Employee attribute, you could see the relationship is automatically
created with title and department name.

Actually the relationship between title and department name is multiple to
multiple, and you could not define a relationship directly between them.
They are actually brideged by Employee attribute.

If anything is unclear, please feel free to let's know.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


================================================== ===

When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.