The load of target data in Bulk mode is a high performance load data mode provided by Informatica. It utilizes the underlying mechanism of the database and relies on the utility provided by the call database itself to load the data.
When using the bulk method load, Informatica calls utility for load, which bypasses the log records of the database to improve database load performance, so the bulk way is not possible rollback operation, It is also not possible to use a database for recover operations. So when you do this property setting, you need to balance the importance of performance improvement and system data recovery.
From the bulk implementation of the way we can know that the bulk mode is mainly for the operation of large amount of data inserts, in other words, do not update. When this option is set, Informatica Sever actually invokes the bulk Utility of the database and ignores the log for loading. So here's the bulk mode, which is the number of transaction submissions we need to adjust. The default value for Commit interval is 10000. So you can increase this value to reduce the number of transactions (Bulk Load Transaction) and 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 and are only related to the size of the write block, which is committed as soon as it is filled.
Because the bulk method can only be used for insert operations. And we know that if we need the update operation, we need to set up the data driven on the session's treat source rows as, and what happens when we choose both settings. If you set both the data driven and bulk mode PowerCenter sever will automatically switch to load in normal mode.
Default bulk to normal settings. Workflow Manager Tools Options Miscellaneous Target Load Type