Universe design question- dealing with contexts and loops

[sonikboom]

Hi All,
We have a schema that roughly correlates to a star schema i.e. When joining
to dimension tables the date_from and date_to columns have to be used in
addition to the id to ensure the correct version of the dimension record is
used.When the dimension record is further joined to another dimension detail
table (snowflake) an additional join has to be performed back to the fact
table in order to get the correct version. This creates loops which have to
be resolved by creating a context for all tables in the schema.e.g.
|------------------------ |
V |
Fact 1 --> dim1 --> dim2

If columns from only fact 1 and dim1 are selected in a report we still see a
join to the dim2 in the SQL generation which I would not have expected to
happen as we are not selecting from that table. Is there any way of ensuring
it does not appear in the SQL without creating multiple contexts as this
will create a large number of contexts which the user will ultimately have
to choose from making it both a maintenance nightmare and difficult for the
users.
I tried to attach a mock universe I have created but unfortunately we are
not allowed to send attachments. If anyone is interested in having a look
at the universe definition I can send it to you if you send me your email.

 

[skrandel]

If you have only 1 fact table in your universe, you likely do not need contexts at all. You likely need some aliases. I can't visualize your problem without seeing your universe.

If you send it to me, I'll take a look. But, I won't be able to give you an answer before Monday.

skrandel@westbaysolution.com


Steve Krandel
Westbay Solutions

http://www.westbaysolutions.com