alternative to IKM Slowly Changing Dimension
AndrisKaMar 14 2009 — edited Feb 17 2010Hi,
I wonder if someone has made alternative IKM so perform slowly changing dimension management, but without its limitations:
1) input always must be one day snapshot of entity versions
2) order of incremental loadings must follow timeline
3) no reload possible for old data, unless manual delete in target + incremental reload day by day assuming source still has data for old periods
4) current record flag required. (we use END_DATE=null as such indicator)
in fact I wanted to solve this SCD task without such limitations as our real life tasks involve correction of past history, and require several days data integration in a time
having this supported from designtime seems logical.
I have made such IKM for Teradata and Oracle technologies ( requires OLAP functions)
Input to IKM is required to be a fact list, basically array of daily snapshots, however by design there is no difference what precision history periods are.
target columns specified using ODI SCD attributes of target datastore.
Sure payload is bigger than standard SCD Type2 solution. but maintenance and reusability benefit is quite impressive.
if someone is interested I'd like to discuss edge use cases.
unfortunately testing effort for such universal historization solution is enormous. Combination count of source facts and target history periods is huge.
andris