Answer / archie

Sri has just said the oposite

Answer / rajasekar genji

yes Archie is right has the name indicates bulk, data will
loaded has bulk we cannot recover in bulk. In Normal mode
data will be loaded one by one so data can be recovered.

Answer / priya

Normal mode creates a session log and is used in session
recovery.
But in Bulk mode its faster in peformance but its not
possible to create a session recover.

Answer / nivas

Target Loading types are mainly catagorized into 2 types
1.Normal Loading
2.Bulk Loading

In the permoance Point of view Bulk Loading is better than
Normal Loading but session recovery is not possible because
of it's Byparses the session log.

Normal loading create the session log for session recovery.
Using Normal Loading only we will get session recovery.

Answer / pardhu

when u configure the session with the type normal the I.S
writes the data records to database log before inserting the
rows into target. when u configure the session with the type
bulk the I.S bypasses the database log it inserts the
records directly into target. In normal mode session
recovery is possible but in bulk mode session recovery is
not possible. bulk mode improves the performance.

Answer / guravareddy

When u chose target load type Normal mode the integration service creates database log and is used in session
recovery.
Where as in bulk mode the integration service by pass load the data into target, but its not
possible to create a session recover.
But in Bulk mode its faster in peformance.

Answer / kumar

Hi Friends,

Normally we have two types of loading. 1, Normal and 2. Bulk.

1 Normal: in this, data will load record by record and the integration service creates database log and is used in session because IS maintain the session log.

2 Bulk: In this, Data will insert Group of records, obviously bulk load will give better performance.

thanks,
kumar

Answer / sri

Bulk mode always create a session log and is used in
session recovery for eg . if we opt for bulk mode, if the
session fails after inserting 9000 rows on total of 10,000
rows (commit interval is after 10,000 rows) then we can
recover 9000 rows and can satrt the session for the rest of
row
In normal mode session log is not created and hence it is
faster than bulk mode .. Session recovery is not possible
in normal mode ..

What are steps to follow Informatica migration from 7x to 8x? Pls Explain...

1 Answers   CTS, TCS,

I have Employee table, 10 cols are connected to next transformation, only 4 cols are selected in SQL override. What would be passed to next col.

5 Answers   BirlaSoft,

Can we call a stored procedure from a unix script which is run using command task

1 Answers   TCS,

what is the difference between copy object import objects using repositery manager which one is best

1 Answers   TCS,

4 yrs etl devloper roles and responsibilities?any body give solutions

0 Answers   TCS,

what is row level and column level indicator?

1 Answers   TCS,

what is lookupoverriding?

1 Answers  

where actually the usage of push down optimization happens...

2 Answers  

What is informatica?

0 Answers  

Hi, I have one flatfile as target in a mapping . When i am trying to load data second time into it. The records already is in flatfile is getting override. I don't want to override existing records. Note : we can do this by implementing CDC / Incremental pool logic if target is relational . But this is flatfile. So, even i use this same technique it will override only So what is the solution ? Is there any option at session level for flatfile target ? Advance Thanks

4 Answers   IBM,

Why do you use Mapping Parameter and mapping variable?

0 Answers  

what is the logic will you implement to laod the data in to one factv from 'n' number of dimension?

3 Answers