|
Operating Scenarios |
Scroll |
This section covers several operational scenarios likely to be encountered both before and after the initial Capture has been placed into operation including, Intial Loads and Target Refresh, changes in the scope of data capture and additional use or processing of the captured data by downstream Engines.
One factor to consider when contemplating or implementing changes in an operational configuration is the implementation sequence. In particular processes that will consume captured data must be tested, installed and operational before initiating capture in a production environment. This is critical because the volume of captured data can overwhelm transient storage if the processes that will consume the captured data are not enabled in a timely fashion.
While the examples in this section will generally proceed from capture of changed data to the population of the target by an Engine, it is essential to fully understand the expected results before configuring the data capture, for example:
•A new column added to a target table is populated from an existing table by an existing engine; while the Engine would be changed to accommodate the new column, NO CHANGES would be required in the existing capture configuration.
•A new table maintained by a new transactions that will be the source of data for a new data warehouse target table will require configuration changes from one end to the other.
The examples below include some common scenarios encountered during and after an initial implementation has proven successful. Review the examples in sequence when thinking about how to implement your own new scenario:
•Initial Target Load and Refresh
