[AccessD] Data Warehouse

Ok, thanks for clarifying.

Charlotte 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert L.
Stewart
Sent: Friday, July 27, 2007 11:13 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Data Warehouse

Charlotte,

In the case of a customer dimension, it would be the customer primary
key from the customer table in the source. The problem comes from having
multiple sources. Then you have to use a surrogate key and store the
source primary key in a column along with the source name.

Sorry, I have been doing it for so long, it is second nature.
So, I do not really think about it.

Robert

At 12:00 PM 7/27/2007, you wrote:
>Date: Thu, 26 Jul 2007 13:59:09 -0700
>From: "Charlotte Foust" <cfoust at infostatsystems.com>
>Subject: Re: [AccessD] Data Warehouse (Was:  Primary Key Best
>         Practices)
>To: "Access Developers discussion and problem solving"
>         <accessd at databaseadvisors.com>
>Message-ID:
>
<F55048AF7E974F429BB24597D7355EEA4BA4C2 at INFOSERVER04.infostat.local>
>Content-Type: text/plain;       charset="us-ascii"
>
>Yes, and I have several of Ralph Kimball's books on Data Warehouse 
>design and I've built a few, but what I was looking for was an 
>explanation of how a dimension table inherits a single column PK  "from

>the source primary table."  I assume it means that all the distinct 
>values for that column that exist in the primary table have a matching 
>PK in the dimension table, but it took me a while to sort it out to 
>that, and I've *worked* with the things!
>
>Charlotte Foust


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com