Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...


What are the mapings that we use for slowly changing
dimension table?

Answers were Sorted based on User's Feedback



What are the mapings that we use for slowly changing dimension table?..

Answer / surya

slowly changing dimensions can be classified by three types.
1)Type1:In this dimension we can store only current data
and here insert are treated as inserts and updates are
treated as updates.
2)Type2:In this dimension we can store complete historic
data and it can divided into three types
a)Flag
b)Version
c)Date Range
But in type2 inserts are treated as inserts and updates are
treated as inserts.
3)Type3:In this dimension we can store One time historic
data with current data.Here also inserts are treated as
insert and updates are treated as updates.

It's depend upon the granularity of the organization.

Is This Answer Correct ?    4 Yes 0 No

What are the mapings that we use for slowly changing dimension table?..

Answer / swetha

Type1: Rows containing changes to existing dimensions are
updated in the target by overwriting the existing dimension.
In the Type 1 Dimension mapping, all rows contain current
dimension data.

Use the Type 1 Dimension mapping to update a slowly changing
dimension table when you do not need to keep any previous
versions of dimensions in the table.

Type 2: The Type 2 Dimension Data mapping inserts both new
and changed dimensions into the target. Changes are tracked
in the target table by versioning the primary key and
creating a version number for each dimension in the table.

Use the Type 2 Dimension/Version Data mapping to update a
slowly changing dimension table when you want to keep a full
history of dimension data in the table. Version numbers and
versioned primary keys track the order of changes to each
dimension.

Type 3: The Type 3 Dimension mapping filters source rows
based on user-defined comparisons and inserts only those
found to be new dimensions to the target. Rows containing
changes to existing dimensions are updated in the target.
When updating an existing dimension, the Informatica Server
saves existing data in different columns of the same row and
replaces the existing data with the updates.

Is This Answer Correct ?    3 Yes 0 No

Post New Answer

More Informatica Interview Questions

What is use of batch file in informatica? How many types of batch file in informatica?

2 Answers   EXL,


Is it necessary to maintain the primary-foreign key relation ship between the targets in informatica while loading using constarint based loading or it is required only at database level ??

1 Answers   IBM,


Hi, Can you please send me the Informatica 8 certification exam dumps to my email id rwork.san@gmail.com Thanks, Revathi.

6 Answers   CTS,


How to load data in informatica ?

0 Answers  


How to display session logs based upon particular dates. If I want to display session logs for 1 week from a particular date how can I do it without using unix. ?

0 Answers   CTS,


What is event and what are the tasks related to it?

0 Answers  


How many numbers of sessions can one group in batches?

0 Answers  


for ex: in source 10 records are there with column sal. use a filter transformation condition as Sal=TRUE and connect to target. what will happen.

11 Answers   Accenture,


What is the difference between informatics 7x and 8x and what is latest version?

0 Answers  


In which circumstances that informatica server creates Reject files?

2 Answers  


Hi I have two sources like A, B. My source A contain 10000 million records from that i need 20 attributes. My source B has also same 10000 million records from that i need only 1 attribute. By using Joiner i have to load into target? Is there any issue regarding this? if issue is there how to tune this mapping in best way?

2 Answers   Zensar,


Explain why we use partitioning the session in informatica?

0 Answers  


Categories