Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Dimension with a link to another dimension

Dimension with a link to another dimension

Dimension with a link to another dimension


I was wondering how people usually deal with dimension attributes that are really other dimensions. For instance, a product with a product group. I need my product group to be "translatable" to other languages so I wanted to treat it as a separate type 1 dimension. But then this means that users have to join from the fact to the product to the product group. And I don't want to go update the fact by putting the product group in each fact row neither... Is this something really wrong or do people end having to live with it? In Kimball's book I don't really see anything about it so I'm wondering how this is handled typically...



RE: Dimension with a link to another dimension

use translation columns.  If your dimension is in english and you need to present it in spanish then add the columns to show the attributes needed in spanish.  MS SSAS allows a cube to show multiple languages by utilizing translation columns.

RE: Dimension with a link to another dimension

That is one way. Another way is to store all descriptions in an other table with a composite key: (text_ID, language). All text fields are stored as an ID.
It creates a form of snowflake but you are very flexible in storing all different languages.

RE: Dimension with a link to another dimension

Hi Hans63,

Yes that is exactly what I am going for. While originally I did not want to have to go with a snowflake schema I think I might have to in some occasions. I can always use views to put a layer of 'abstraction' on top for users who will query it.



Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close