RE: how can u implement slowly changed dimensions in d...
Yes, we can join a flat file and database in an indirect way. First create a job which can populate the data from database into a Sequential file and name it as Seq_First. Take the flat file which you are having and use a Merge Stage to join these two files. You have various join types in Merge Stage like Pure Inner Join, Left Outer Join, Right Outer Join etc., You can use any one of these which suits your requirements.
RE: can u join flat file and database in datastage?how?
Yes, we can do it in an indirect way. First create a job which can populate the data from database into a Sequencial file and name it as Seq_First1. Take the flat file which you are having and use a Merge Stage to join the two files. You have various join types in Merge Stage like Pure Inner Join, Left Outer Join, Right Outer Join etc., You can use any one of these which suits your requirements.
RE: how can u implement slowly changed dimensions in d...
SCDs are three typesType 1- Modify the changeType 2- Version the modified changeType 3- Historical versioning of modified change by adding a new column to update the changed data
RE: how can u implement slowly changed dimensions in d...
yeah u can implement SCD's in datastage
SCD type1
just use 'insert rows else update rows'
or
' update rows else insert rows' in update action of target
SCD type2
u have use one hash file to look -up the target ,take 3 instance of target ,give diff condns depending on the process,give diff update actions in target ,use system variables like sysdate ,null
RE: how can u implement slowly changed dimensions in d...
We can handle SCD in the following waysType I: Just overwrite; Type II: We need versioning and dates; Type III: Add old and new copies of certain important fields. Hybrid Dimensions: Combination of Type II and Type III
RE: how can u implement slowly changed dimensions in d...
yes you can implement Type1 Type2 or Type 3. Let me try to explain Type 2 with time stamp.
Step :1 time stamp we are creating via shared container. it return system time and one key. For satisfying the lookup condition we are creating a key column by using the column generator.
Step 2: Our source is Data set and Lookup table is oracle OCI stage. by using the change capture stage we will find out the differences. the change capture stage will return a value for chage_code. based on return value we will find out whether this is for insert , Edit, or update. if it is insert we will modify with current timestamp and the old time stamp will keep as history.
