Ciao e buongiorno a tutti!!!
I wanna ask to everybody this question:
I'm modelling a DRM; my time dimension (denormalized table) is (more or less) this:
TIME_ID_DAY - number - PK
LANGUAGE_CD - varchar - PK
TIME_DT - date
WEEK_CD - varchar
MONTH_CD - varchar
MONTH_DESC - varchar
QUARTER_CD - varchar
YEAR_CD - varchar
So, the couple TIME_ID_DAY-LANGUAGE_CD is the PK but I apply filter on the source (#sq($Language_lookup{ $runLocale})#) and I don't "need" it in my REGULAR DIMENSION, in the sense I want to show to the user just the member TIME_CD for the level "DAY". (I hope my english is quite good...)
However, now I have to add determinats in this query subject: I was asking to myself...
the key of determinant for DAY should to be:
a) the couple TIME_ID_DAY-LANGUAGE_CD (and all the other columns are attributes) that's the key in my table but I don't show to the user
b) the column TIME_CD (that is going to be unique because, as I said, I apply a filter on the QS)
what do you think?
Please... any answer is wonderfull!!!
ciaoooooooo :)
Hi,
It does not matter, whether you show the key to user or not while making any key as determinant unique key.
You can go ahead with option A to apply it as an determinant unique key.
If anyone has any other point of view, pls. suggest.
Regards,
~Harish