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.
is pronounced ree-bar and is a Modenism for R
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.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs