Informatica Bulk and Normal mode in-depth explanation

The Bulk approach to load the target data is a high-performance load data method that Informatica provides. It uses the database underlying mechanism to load data by invoking the utility provided by the database itself.

with bulk load, Informatica calls utility for load, which bypasses the log records of the database to improve the load performance of the database, so the bulk method is not possible to rollback operations. It is also impossible to use the database for recover operations . So when this property is set, it's important to balance performance gains with system data recovery.

from the bulk implementation of the way we can know, the bulk mode is mainly for large data volume insert operation, in other words, do not update. When this option is set, Informatica Sever actually calls the database's bulk Utility and ignores the log for loading. So here's how you can tune the bulk mode, which is the number of transaction commits we need to adjust. The default value for Commit interval is 10000. Therefore, you can increase this value to reduce the number of transactions (Bulk Load Transaction) to improve performance. It is important to note that this adjustment is only useful for Oracle and SQL Sever. DB2 and Sybase are not affected by this value, they are only related to the size of the write block and are committed once they are full.

Because the bulk method can only be used for insert operations. And you know that if we need an update, we need to set it to data driven in the session's treat source rows as setting, and what happens when we choose both settings. If you set both data driven and bulk mode PowerCenter sever will automatically switch to load using normal mode.

Note that the target load type has an index using normal. Using bulk without indexing is faster.

Informatica Bulk and Normal mode in-depth explanation