SCD dimension
2 posters
Page 1 of 1
SCD dimension
Helou,
I have two dimension where I need handle the changes. I read that we can do this with validation dates or we can use
a version row (fk pk data data data version 0 , fk pk data data data version 1) and than we use fk.
My co workers ant to handle changes in a way I do not like.
FAct table
Primary keyof persons, serial number, other data...
Dimension of persons
Primary key name, surname, gender, serial number
Dimension
10, John, Kine, M, 01
10, John, Zupan, M, 02
11, Jane, Coop, F, 01
.... Thanks K
I have two dimension where I need handle the changes. I read that we can do this with validation dates or we can use
a version row (fk pk data data data version 0 , fk pk data data data version 1) and than we use fk.
My co workers ant to handle changes in a way I do not like.
FAct table
Primary keyof persons, serial number, other data...
Dimension of persons
Primary key name, surname, gender, serial number
Dimension
10, John, Kine, M, 01
10, John, Zupan, M, 02
11, Jane, Coop, F, 01
.... Thanks K
MK- Posts : 16
Join date : 2013-02-04
Location : Slovenia
Re: SCD dimension
Usually you use a timestamp instead of a version number. The problem with version numbers is you need to figure out what the last one was to set the new one. You will also need a 'current' flag to identify the most current row.
Also the surrogate PK is different on each row.
Also the surrogate PK is different on each row.
SCD dimension
Hi,
Thanks for your replay, they said that on event day from fact table will be in the same row key of the person and the verzion number.
From dimension of person we will take the max version. I do not know how to explain them, that the standard method (fk in fact table and
date (or timestamp) from where is valid that is better way.
Thanks again for all your help, K
Thanks for your replay, they said that on event day from fact table will be in the same row key of the person and the verzion number.
From dimension of person we will take the max version. I do not know how to explain them, that the standard method (fk in fact table and
date (or timestamp) from where is valid that is better way.
Thanks again for all your help, K
MK- Posts : 16
Join date : 2013-02-04
Location : Slovenia
![-](https://2img.net/i/empty.gif)
» bridge table and junk dimension on customer dimension (bank/credit union)
» modelling Product dimension for Pizza outlet
» How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)
» Tip #136 Adding a Mini-Dimension to a Bridge Table: What if you can't split the dimension?
» Using the Date Dimension for Summary Fact Tables or new specialized Month Dimension?
» modelling Product dimension for Pizza outlet
» How to handle a Type I or II dimension with a snowflaked customer sub dimension (kimball book page 337, 338)
» Tip #136 Adding a Mini-Dimension to a Bridge Table: What if you can't split the dimension?
» Using the Date Dimension for Summary Fact Tables or new specialized Month Dimension?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|