Answer Posted / rakesh

The main difference between normal and bulk load is, in normal load Informatica repository service create logs and in bulk load log is not being created. That is the reason bulk load loads the data fast and if anything goes wrong the data can not be recovered. But in normal load since the log is created the lost data can be recovered.

By configuring session to Bulk loading we cannot do 'session recovery' when it get failed whereas in normal loading we can easily do session recovery.

Note:In normal load Informatica creates logs record by record in database level and in bulk mode it will not create detail log. By avoiding that detail writing in bulk mode improve performance.

Note:If there are indexes and constraints in the table, you cannot use Bulk Load
You can drop/disable those indexes/constraints (pre session ) , then load the data (use Bulk Load) , and then create/enable the indexes/constraints (post session )

What are the limitations of joiner transformation?

1110

---

How you know when to use a static cache and dynamic cache in lookup transformation?

1853

---

What are junk dimensions?

1068

---

Mention few power centre client applications with their basic purpose?

951

---

hi real timers . iam waiting for ur reply regarding ETL TESTING

2269

---

Define enterprise data warehousing?

1201

---

What are the components of the workflow manager?

1133

---

The question was on time stamp. what is the difference between HH and HH24 when to use when.

2055

---

What are the tuning techniques you applied during your last project

2024

---

list out all the transformations which use cache?

1180

---

What is a code page?

1175

---

In What Situations we can use MappingParameters ,Mapping Variables AND Session Parameters in REAL TIME.

2062

---

Explain what are the different types of transformation available in informatica.

1142

---

What is update strategy transform?

1100

---

Clarify the aggregator change?

1024

---