SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Updating Historical Information


Updating Historical Information

Author
Message
SA-1
SA-1
SSCommitted
SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)SSCommitted (1.5K reputation)

Group: General Forum Members
Points: 1517 Visits: 944
I have to create a slowly changing dimension with the caveat that any of the data attributes can change for any of the records (even the historical one's). There is a surrogate key from the source system that i could store locally but i was wondering if anyone has run in to this situation and used a different option / design.
Antti Tikka
Antti Tikka
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 144
I haven't implemented this kind of situation but I think that the most elegant way is to store surrogate key of the source table to data warehouse table and use this as a business key in slowly changing dimension component.
I have used surrogate key of the source table as a business key many times in different situations.
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (85K reputation)SSC Guru (85K reputation)SSC Guru (85K reputation)SSC Guru (85K reputation)SSC Guru (85K reputation)SSC Guru (85K reputation)SSC Guru (85K reputation)SSC Guru (85K reputation)

Group: General Forum Members
Points: 85428 Visits: 41078
SA-1 (11/5/2013)
I have to create a slowly changing dimension with the caveat that any of the data attributes can change for any of the records (even the historical one's). There is a surrogate key from the source system that i could store locally but i was wondering if anyone has run in to this situation and used a different option / design.


I'm always amazed by such things. Historical table data is NOT supposed to change. By definition, it's supposed to be historical and, therefor, never change. Changing historical information may keep your company from getting ISO, SOX, and SEC certifications and, if something really bad happens, could even land everyone involved in jail.

I strongly recommend that the company get out of the nasty habit of changing historical information whereever it is kept.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search