The repository objects such as mapping, session, workflows, etc. can be taken back up into a .xml file format.
Since the records are entered into the database log, the integration service can perform a rollback on transaction errors.
As a result, the integration service can perform session recovery.
Since the records are passing to the target viva database log the integration service "increases the data loading time".
Desired to gain proficiency on Informatica? Explore the blog post on Informatica training to become a pro in Informatica.
The session which is configured for bulk loading loads the high volumes of data into the target and increases session performances. When you configure the session with the bulk loading the integration service bypass the database log and enters the records into the target.
Since the integration service bypass the database log, it can't perform a rollback on transaction error.
As a result, the integration service can't perform the session recovery.
The integration service does not support bulk loading into index target table.
Load records increase because the record loaded target directly.
Don't create a primary key in the target database but however, you can primary in the target designer.
Select the mapping tab set the reader and writer connection with target Load type "BULK".