We help IT Professionals succeed at work.

Freeze portion of datamart

jvoconnell asked
Last Modified: 2017-04-06

We have a data mart that contains data going back 6 to 7 years. Up until now we usually roll off the earliest year. Users have requested not to roll off data any longer as well as going back earlier in time and adding more data. The older data is static. Currently our data mart process is a drop and replace. We use all surrogate keys.

My question is what are the thoughts for the best method for not having to refresh the fact and dimension tables for that older static data so as to keep the build time manageable.

Sorry in advance for the newbie methods we have thought about implementing. One idea was to build  the DM as normal with all the required data to satisfy user requirements. We thought about  finding the max Identity (PK) in each fact and dimension for records that would remain static and also set a flag on those records. Then each month delete the years of data that would need to get refreshed and perhaps reseed the table based on the highest value of the static data. Then just process the newer set of data and appending to the fact and dimensions.

We are probably way off base here. So please excuse the ignorance on our part.

Any insight is appreciated.
Watch Question

Database Analyst
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)


This is great. This wasn't the type of question that I would expect to get an answer I could immediately implement. I do want people to know that some research was done prior to my post but our searches didn't return much valuable. We can take what you have provided and know discuss what will work best for us. Thank you so much! You guys are great.