You are on page 1of 7

SCD Type 1 Implementation using Informatica PowerCenter

Johnson Cyriac | Jan 30, 2013 | ETL Design | Mapping Tips

Unlike SCD Type 2, Slowly Changing Dimension Type 1 do not preserve any history versions of data. This methodology overwrites old data with new data, and therefore stores only the most current information. In this article lets discuss the step by step implementation of SCD Type 1 using Informatica PowerCenter.

The number of records we store in SCD Type 1 do not increase exponentially as this methodology overwrites old data with new data Hence we may not need theperformance improvement techniques used in the SCD Type 2 Tutorial.

Understand the Staging and Dimension Table.

Slowly Changing Dimension Tutorial Series Part I : SCD Type 1. Part II : SCD Type 2. Part III : SCD Type 3. Part IV : SCD Type 4. Part V : SCD Type 6. For our demonstration purpose, lets consider the CUSTOMER Dimension. Below are the detailed structure of both staging and dimension table.

Staging Table
In our staging table, we have all the columns required for the dimension table attributes. So no other tables other than Dimension table will be involved in the mapping. Below is the structure of our staging table.

Key Points
1. Staging table will have only one days data. Change Data Capture is not in scope. 2. Data is uniquely identified using CUST_ID. 3. All attribute required by Dimension Table is available in the staging table

Dimension Table
Here is the structure of our Dimension table.

Key Points
1. CUST_KEY is the surrogate key. 2. CUST_ID is the Natural key, hence the unique record identifier.

Mapping Building and Configuration


Lets start the mapping building process. For that pull the CUST_STAGE source definition into the mapping designer.


Now using a LookUp Transformation fetch the existing Customer columns from the dimension table T_DIM_CUST. This lookup will give NULL values if the customer is not already existing in the Dimension tables.

LookUp Condition : IN_CUST_ID = CUST_ID Return Columns : CUST_KEY


Use an Expression Transformation to identify the records for Insert and Update using below expression.


Additionally create two output ports.




See the structure of the mapping in below image.


Map the columns from the Expression Transformation to a Router Transformation and create two groups (INSERT, UPDATE) in Router Transformation using the below expression. The mapping will look like shown in the image.
o o




Every records coming through the 'INSERT Group' will be inserted into the Dimension table T_DIM_CUST.

Use a Sequence generator transformation to generate surrogate key CUST_KEY as shown in below image. And map the columns from the Router Transformation to the target as shown below image.

Note : Update Strategy is not required, if the records are set for Insert.

Step 6

Records coming from the 'UPDATE Group' will update the customer Dimension with the latest customer attributes. Add an Update Strategy Transformation before the target instance and set it as DD_UPDATE. Below is the structure of the mapping.

We are done with the mapping building and below is the structure of the completed mapping.

Workflow and Session Creation

There is not any specific properties required to be given during the session configuration.

Below is a sample data set taken from the Dimension table T_DIM_CUST. Initial Inserted Value for CUSTI_ID 1003






Hope you guys enjoyed this. Please leave us a comment in case you have any questions of difficulties implementing this.