Scribd
Upload
41 views7 pages

I Am Using Aliases For Physical Tables. For Time There Is One Physical Table DIM - TIME and Four Aliases Which You Can See On Below Screen

This document discusses using aliases for physical tables in a data model, including a DIM_TIME table and four time dimension aliases. Each alias and fact table has a key and foreign keys linking them to other dimension aliases. The physical model works with a time hierarchy on case creation date but errors occur when adding a hierarchy on case last update date or creating hierarchies in a different order.

Uploaded by

Firas Chaabene
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
41 views7 pages

I Am Using Aliases For Physical Tables. For Time There Is One Physical Table DIM - TIME and Four Aliases Which You Can See On Below Screen

This document discusses using aliases for physical tables in a data model, including a DIM_TIME table and four time dimension aliases. Each alias and fact table has a key and foreign keys linking them to other dimension aliases. The physical model works with a time hierarchy on case creation date but errors occur when adding a hierarchy on case last update date or creating hierarchies in a different order.

Uploaded by

Firas Chaabene
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

I am using aliases for physical tables.

For Time there is one physical table DIM_TIME and four aliases
which you can see on below screen

Each alias has a key:


“Case” dimension which is alias for fact table you can see below:
It also has a key:

And foreign keys to other dimensions (being aliases):


Fact table which is also an alias has foreign key to the “Case” dim:

And the entire physical model looks like this:


And business model which is not completed yet:

Time hierarchy on Case creation time works perfectly fine but when I add time hierarchy on Case last
update time I get error:

So It is working fine for only first hierarchy. I tried to create first Case last update time hierarchy and
then Case creation time hierarchy – still the same issue but this time for secondly created hierarchy –
Case creation time. The same happens for Date hierarchies.

You might also like