Answer / shrikant

Hello,
If I understand this question properly, it says that the
no. of "Source" columns are changing.
I do not agree with this scenario. Probably in
Datawarehousing, you won't find such a design. As far as
DWH is concerned, it takes the data from the OLTP systems &
after performing some operations (E-extract, T- transform)
it finally loads the data in some targets.
Here, as per the question, the question itself arises for
the OLTP design. No any OLTP (or database design principal)
system suggests a varying number of columns.
So, please do not get confused by such trivial kind of
questions. DWH is a very disciplined subject & it follows a
very good standards. Please go through the concepts first.
You will get a clear picture of DWH then.

Answer / santosh sinha

This is really a confusing question and raise question on
OLTP design butIf we are not changing the design of column
which is used in our mapping then it will not effect the
mapping so increasing the no of column will not effect.

Answer / sam

If your Source is XML this kind of scenario will come.Take
the exact XML DDL (max number of columns)as a source
defination.

Answer / suganthi

We do have a design like this(in DWH to DM load). But to
accomplish this we have created a procedure to add new
columns in teh table.

Answer / bidhar

If this is the requirement,then you will have to reimport
the source metadata in source analyzer and the save so that
the new columns are reflected in the mapping source.But to
pull it to target you need to join manually the pipelines.

But Such type of scenarios rarelly comes in OLAP models.A
good DWH design should be in such a way that if in future
any new columns come in the OLTP systems then DWH can
accomodate that.
For example Product Table has 20 columns in OLTP system.
Then OLAP model can have more than 20 columns for Product
Dimension(ATRIBUTE_1,ATRIBUTE_2 and so on)and populate null
values into that.
Now whenever new columns are added into the OLTP Product
table then we can simply map the new column to the ATRIBUTE
Columns,Keeping the datatypes in mind.

Answer / arnab

This should not happen when executing a datawarehousing
project , This reflects poor design and poor visualisation
of the requirements

The safest way to handle this is re-import the source
definition, someone suggested create a source with the
maxinmum number of columns , there is something called
quality of code and if someone codes like this it is really
a bad example of informatica coding

Answer / srinu

Some one is not agree with Sathish Rajaiah
answer(1 No)ABOVE answer.
Let me Explain Why ?

Answer / rekha

I THINK U CAN DO IT BY MAPPING PARAMETERS

Answer / sathish rajaiah

Create source defination with maximum (depends on the max
numbers of columns u get in the source) number of fields
and use that in the mapping.
ex: create source defiantion with 20 fields and use this in
mapping this wil handle source comes with columns btween 1
to 20.

Note : Above wrks only for flat file sourcse not fr RDBMS
sources

What is IQD file?

1 Answers  

My source is EmpID, Salary- (101, 1000)(102, 2000)(103, 3000). In the Target I want the following EmpID, Salary, Composite_Salary- (101, 1000, 1000)(102, 2000, 3000)(103, 3000, 6000). Please guide on how to build the mapping.

5 Answers   Amdocs,

What are parallel querys and query hints?

1 Answers  

How many cubes create from a single model?

1 Answers  

what happens if you try to create a shortcut to a non- shared folder?

1 Answers  

Different sorts of metadata that stores in the storage facility?

0 Answers  

What is the default join that source qualifier provides?

3 Answers   Informatica,

how we load the data from source to staging area

4 Answers   TCS,

How do you convert single row from source into three rows into target?

0 Answers  

What is a snowflake schema?

0 Answers  

What are the types of metadata that stores in repository?

2 Answers  

how can we check whether a particular cache is static or dynamic?

1 Answers   InfoCepts, TCS,