Installation and Configuration Best Practices › Configuration › Use Incremental Update

Use Incremental Update

Configure components to perform partial database updates periodically throughout the day. For example, if a DB2 region generates 60 million transaction records daily, the DB2 component in a unit can be configured to process the raw data incrementally at 8:00 AM, 2:00 PM, and midnight. Assuming a consistent transaction arrival rate, each update only has to process 20 million records.

Business Value:

Addresses the situation where a large volume raw data source cannot be processed as a whole within an acceptable daily update window. Also supports inter-day reporting.

Additional Considerations:

• Incremental update is activated for a specific component within a particular unit. A unit containing multiple components can use this option for none, one, some, or all components within the unit.
• Overall processing time is increased but spread over the day. The final daily update run completes in less time than if it had to process the complete set of raw data itself.
• An additional incremental update database must be allocated to contain the partially processed data until the final daily update completes.
• Raw data collections must be scheduled to provide input files for the incremental updates.
• Reporting on incremental databases should be controlled by the CA MICS administrator to make sure the database is not tied up when the next incremental update is ready to run.

More Information:

For more information, see Section 4.3.12.6, Incremental Update Considerations, in the Planning, Installation, Operation, and Maintenance Guide.