<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Data Warehousing
»
Strategies and Ideas
»
Slowly Changing dimensions Design and ETL...
Slowly Changing dimensions Design and ETL Help
Rate Topic
Display Mode
Topic Options
Author
Message
3ilabsbiz
3ilabsbiz
Posted Saturday, November 20, 2010 10:41 AM
Forum Newbie
Group: General Forum Members
Last Login: Saturday, November 20, 2010 1:47 PM
Points: 1,
Visits: 2
I have 3 tables in OLTP like Account,Contact,Address related with foreignkey relationship and account has account type attribute, address has city,state,country,zip
How I can design a Dimensional data store with this info. The basic business requirement is to find the no of Accounts from a particular zip code , keeping the history of count if the a customer moves from one location to another. I thought account as Fact , Address as slowly changing dimension with type 2, but then if an address changes then I have to add additional row in Account Fact and not a good design.
What is the logic for relationship based on type 2 SCD.
Any suggestion will be appreciated.
Thanks
Post #1023940
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
Posted Monday, November 29, 2010 1:12 PM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 12:00 PM
Points: 2,988,
Visits: 4,412
3ilabsbiz (11/20/2010)
I have 3 tables in OLTP like Account,Contact,Address related with foreignkey relationship and account has account type attribute, address has city,state,country,zip
How I can design a Dimensional data store with this info. The basic business requirement is to find the no of Accounts from a particular zip code , keeping the history of count if the a customer moves from one location to another. I thought account as Fact , Address as slowly changing dimension with type 2, but then if an address changes then I have to add additional row in Account Fact and not a good design.
What is the logic for relationship based on type 2 SCD.
You do not add an additional row on the FACT table, you add an additional row on the DIM table.
My favorite design for a Type II SCD DIM table is by adding three columns to the design:
- Version
- ValidFromDate
- ValidUntilDate
In my design version=0 is the current version while older versions go 1,2,3,etc.
For rows with version > 0 ValidFromDate/ValidUntilDate tells you "when" that particular row was current.
Hope this helps.
_____________________________________
Pablo (Paul) Berzukov
Author of
Understanding Database Administration
available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Post #1027579
aaa-322853
aaa-322853
Posted Thursday, December 30, 2010 5:02 AM
SSC Veteran
Group: General Forum Members
Last Login: Thursday, May 09, 2013 7:25 AM
Points: 288,
Visits: 674
That's quite an interesting approach with your "Version" field Paul. I can imagine that could prove very useful.
You don't mention a "IsRowCurrent" field however, do you derive this at run time when making SCD changes to your Dims?
Post #1040820
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
Posted Thursday, December 30, 2010 7:27 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 12:00 PM
Points: 2,988,
Visits: 4,412
aaa-322853 (12/30/2010)
That's quite an interesting approach with your "Version" field Paul. I can imagine that could prove very useful.
You don't mention a "IsRowCurrent" field however, do you derive this at run time when making SCD changes to your Dims?
In my design "Version=0" means "CurrentRow" - hope this clarifies
_____________________________________
Pablo (Paul) Berzukov
Author of
Understanding Database Administration
available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Post #1040895
aaa-322853
aaa-322853
Posted Thursday, December 30, 2010 10:44 AM
SSC Veteran
Group: General Forum Members
Last Login: Thursday, May 09, 2013 7:25 AM
Points: 288,
Visits: 674
Oops my mistake, didn't read your original post correctly!
Typically when you have a type 2 you would identify this by comparing to you current record, in your case Version = 0, and then expire it before inserting the incoming record. How do you identify the next version number when expiring your outgoing record? Do you do anything clever here?
Post #1041039
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
Posted Thursday, December 30, 2010 11:17 AM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 12:00 PM
Points: 2,988,
Visits: 4,412
aaa-322853 (12/30/2010)
Oops my mistake, didn't read your original post correctly!
Typically when you have a type 2 you would identify this by comparing to you current record, in your case Version = 0, and then expire it before inserting the incoming record. How do you identify the next version number when expiring your outgoing record? Do you do anything clever here?
-- no problem, the same happens to me all the time.
The beauty of SCD is that the number of changes per ETL cycle is a very small fraction of ETL's total volume so, solution doesn't have to be fantastic, just functional.
When a SCD change happens I read version=0; insert it as version=max(version)+1 including ToTimeStamp; then apply change to version=0 including FromTimeStamp.
Thank you for asking.
_____________________________________
Pablo (Paul) Berzukov
Author of
Understanding Database Administration
available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Post #1041069
jeff122877
jeff122877
Posted Wednesday, January 05, 2011 5:27 PM
Grasshopper
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 10:34 AM
Points: 13,
Visits: 198
I use a current record column which I call is_current. 1 = TRUE, 0 = FALSE. If I wanted to see the order in which that particular records' SCD2 value changed (for example if the record was a contacts address and I wanted to see the order in which they moved from state to state to state), I could simply sort by Start_Date (effective date).
Post #1043428
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
