Answer Posted / senthil

hi,
we already know basic restrictions of view and materialized
view,

view is a logical or virtual table it doesn't have data on
its own, but materialized view has a physical structure it
stores data in local machine or on its own.materialized view
can be refreshed automatically or manually. but in view, if
any changes happened in the base tables, we want to reflect
the same in the view means view has to issue the select
statement again to the database

Source and Target are flat files, Source table is as below ID,NAME 1,X 1,X 2,Y 2,Y On Target flat file i want the data to be loaded as mentioned below ID,NAME,REPEAT 1,X,2 1,X,2 2,Y,2 2,Y,2 How to achieve this, Can i get a map structure

7298

---

differences between service based and product based?

1979

---

What is joiner transformation?

965

---

Explain how many types of dimensions are available in informatica?

1032

---

Tell me about your experience in informatica? what is best mark you can give yourself? How to answer this question?

8177

---

What is the need for an etl tool?

1027

---

Explain the mapping variable usage example in informatica

1101

---

Reusable transformation and shortcut differences

1799

---

Where is metadata stored?

1059

---

What is the surrogate key?

1175

---

How does a rank transform differ from aggregator transform functions max and min?

1163

---

What is the scenario which compels informatica server to reject files?

1024

---

Briefly describe lookup transformation?

994

---

What are the types of schemas we have in data warehouse.

914

---

How is union transformation utilized?

964

---