I have had many requests to share best practices when using IBM InfoSphere Change Data Capture (from this point forward in the blog referred to as CDC). I will try to add new tips and techniques on a regular basis.
Along with many of the best practices posts, I will include items denoted by "Rule of Thumb". These are general guidelines that will help in your planning. I will endeavor to provide reasons or context for the guidance. The Rules of Thumb should not be treated as hard limits, rather as useful guidance. If your needs fall significantly outside the guidance, it certainly does not mean that it can not be done. Rather, it would be best to engage with an InfoSphere CDC subject matter expert, and potentially you may want to consider IBM Services for assistance.
- Best Practice - Logging Requirements
- Best practice - Log Retention Policies
- Best Practice - Required CPU on Source
- Best Practice - Memory Requirements on LUW
- Best Practice - Target Considerations
- Best practice - Number of CDC instances Required
- Best practice - Number of Subscriptions per CDC Instance
- Best practice - Number of CDC Subscriptions Required
- Best Practice - Number of Tables in a Subscription
- Best Practice - Single Scrape
- Best Practice - Long Running & Large Transactions
Steady State Operations
- Best practice - Setting up Notifications (Alerts & Alarms)
- Best Practice - Things to know that you may not be aware of