Hi Guy Rogers,
Table comparison (as per its definition) compares two tables and produces difference between the two tables (Source and compared table) as data sets with op-codes pushed on them.
TC --> QT --> TC scenario.
First TC produces the output of datasets with different op-codes (Insert, Update and Delete) and when it is consumed by a QT it will be nullified. To have those Op-codes present on the data and for the system to understand that, you need to use Map Operation transformation.
So that’s the reason for that warning.
Try using TC --> Map_Operation and think this warming might go.
Thanks
Rakesh 