There is significant development effort developing DataStage jobs for each additional table added to replication.When integrating with DataStage, there are two independent GUIs for configuration, and two places required to monitor the replication stream.Having a resilient CDC installation is more complex if DataStage is also involved.Adding DataStage into the replication stream introduces additional points of failure.The exception to this rule is when targeting Teradata, if you use DataStage flat file integration, the throughput will be higher than CDC direct to Teradata.Performance going through DataStage (no matter which integration option is chosen) will be significantly slower than applying via a CDC target directly to the database.Complex transformations are required that could not be handled natively with CDC, such as complex table look-upsĬons of replicating from CDC to DataStage to an eventual target database:.You need to target a database that CDC doesn't directly support and is not appropriate for CDC FlexRep.do not add DataStage to the mix).ĬDC integration with DataStage is the right solution for replication when: If possible, the best solution is always to use CDC direct replication (i.e. The deployment option selected will significantly affect the complexity, performance, and reliability of the implementation. There are many deployment models available for InfoSphere Data Replication's CDC technology of which DataStage integration is a popular one. Best Practice - CDC / CDD to DataStage Integration
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |