maintaining history data

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
tostay2003
Participant
Posts: 97
Joined: Tue Feb 21, 2006 6:45 am

maintaining history data

Post by tostay2003 »

Hi All,

This seems to be another simple question to you all. But a bit tough for me :( .

I have here with me a prototype of ETL jobs done. This now needs to go up against the database.

Now I need to come to conclusions as to how to maintain the history data. Because everytime job is executed, fresh data will be loaded into the target.

Can you give me few suggestions

a) regarding when to populate surrogate key, how to and from which stage (i.e. after surrogate key or before surrogate key) should the history data be fetch to the input.

b) how to decide on type 1, type 2, type 3.

c) Any suggestions as to what more columns (like flags) or anything else is needed to accomplish this.

The question seems blurry, but its blurry for me as well. Please do as well tell me what i need to take into consideration from the input data to proceed with the steps to maintain history data.

With Regards

thank you
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Get yourself a copy of The Data Warehouse Lifecycle Toolkit by Ralph Kimball and others (published by Wiley). Chapters 4 through 7 will be of particular use in answering this question. It's a full exposition of the requirements and techniques of dimensional modelling.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply