• I was able to implement that by adding expressions in the DFT components to make it disable based on project parameter per table.

    When I tried the following scenario I found surprise:

    I did the initial run with 3 tables and all populated successfully. Then I UPDATED table#1 (didn't run the incremental pkg yet). I then added table#4 DFT to the initial run package and ran it to populate table#4 only. Now, I ran the incremental load package so that the previous update to table#1 shows up in destination table. But NO.... it didn't happen. It seems the initial pkg run to load new table#4 after updating table#1 reset the CDC status and it lost the track for the update.

    How to solve that? I should not rerun everything again once I add a new table to the CDC implementation. Any lead will be greatly appreciated.