Bookshelf Home | Contents | Index | PDF |
Siebel Enterprise Integration Manager Administration Guide > EIM: Examples of Common Usage > Other Examples > Example: Transaction Logging with Row-by-row Processing versus Set-based ProcessingTransaction logging is enabled and disabled from within the System Preferences view in the Administration - Application screen. The preference is called Docking: Transaction Logging. You can also adjust the transaction logging system preference setting by changing the LOG TRANSACTIONS parameter in the EIM configuration file. For more information, see Process Section Parameters Generic to All EIM Processes. LOG TRANSACTIONS and SET BASED LOGGING ParametersEIM performs row-by-row (RBR) transaction logging when LOG TRANSACTIONS is set to TRUE and SET BASED LOGGING is set to FALSE in the .IFB file. In row-by-row logging mode, EIM fetches all the data to the client. Most of the time, SET BASED LOGGING is not explicitly set. When SET BASED LOGGING is not explicitly set, the Docking: Transaction Logging system preference is used to determine the processing method. When Docking: Transaction Logging is disabled, all operations (insert, update, and delete) are performed in set-based mode. If you explicitly set LOG TRANSACTIONS = FALSE in the .IFB file, then EIM does not log any transactions into the Master Transaction Log table. When Docking: Transaction Logging is enabled, all inserts and deletes are performed in set-based mode, while updates are performed in RBR mode. When Docking: Transaction Logging is set to TRUE, EIM logs transactions into either the .DX files or the S_DOCK_TXN_LOG table, depending on the setting for LOG TRANSACTIONS TO FILE in the .IFB file. When SET BASED LOGGING is explicitly set, EIM uses the value of this parameter to determine the processing mode. When SET BASED LOGGING is TRUE, all operations (insert, update, delete) are performed in set-based mode. When SET BASED LOGGING is FALSE, all operations are performed in RBR mode. For import and delete processes, it is not recommended that the SET BASED LOGGING parameter be set to TRUE because in most cases, there is no reason to set this parameter explicitly. For merge processes, SET BASED LOGGING must be set to FALSE for transaction logging to work properly. To log every transaction separately, EIM changes its operation mode to RBR. Logging Locations for LOG TRANSACTIONS and LOG TRANSACTIONS TO FILEWith RBR processing, data is logged according to one of three scenarios:
When to Use Row-by-Row ProcessingFor import and delete processes, you should let EIM determine which mode to use. EIM will use the method with the best performance for the functionality requested. For initial data loading, you can disable transaction logging for improved performance (EIM will use set-based mode for all operations). For ongoing operations with Mobile Web Clients, transaction logging should be enabled (EIM will choose set-based logging for inserts and deletes, and RBR for updates). For merge processes with transaction logging enabled, you must explicitly set EIM to run in RBR mode in order for transaction logging to work properly. The following are examples of cases when RBR logging should be used:
Advantages and Disadvantages of Using RBR LoggingAdvantages of RBR logging include the following:
A disadvantage of RBR logging is that RBR logging affects performance, especially with large imports and deletes. |
Siebel Enterprise Integration Manager Administration Guide |