Re: Design question
From: Geoff Muldoon <geoff.muldoon_at_trap.gmail.com>
Date: Sat, 21 Feb 2009 11:49:37 +1100
Message-ID: <MPG.2409e1f1b0f0acb5989727_at_news.x-privat.org>
Matthias Hoys says...
>
> "Mladen Gogala" <gogala.mladen_at_gmail.com> wrote in message
> news:gnebgm$hfl$2_at_solani.org...
> > On Tue, 17 Feb 2009 00:57:55 -0800, matthias.hoys wrote:
> >
> >> Would this be ok:
> >> - dimension table "Location'
> >> - dimension table "Time"
> >> - dimension table "Temperature"
> >> - fact table "Measurements": location_id, time_id, maxtemperature_id,
> >> mintemperature_id etc ...
Date: Sat, 21 Feb 2009 11:49:37 +1100
Message-ID: <MPG.2409e1f1b0f0acb5989727_at_news.x-privat.org>
Matthias Hoys says...
>
> "Mladen Gogala" <gogala.mladen_at_gmail.com> wrote in message
> news:gnebgm$hfl$2_at_solani.org...
> > On Tue, 17 Feb 2009 00:57:55 -0800, matthias.hoys wrote:
> >
> >> Would this be ok:
> >> - dimension table "Location'
> >> - dimension table "Time"
> >> - dimension table "Temperature"
> >> - fact table "Measurements": location_id, time_id, maxtemperature_id,
> >> mintemperature_id etc ...
> I have an additional question regarding the "Temperature" dimension. These
> are values like 10.34, 25.40, -0.19 ... so these are floating point values
> with a precision of 2 numbers.Should I create a separate dimension for this
> attribute (with foreign keys mintemperature_id, maxtemperature_id in the
> Facts table) or just put them as such in the facts table ? I don't see the
> real advantage of creating a separate dimension for them ?
Temperature as you describe is a fact attribute, not a dimension.
Geoff M Received on Fri Feb 20 2009 - 18:49:37 CST