Adding a transform to an existing task/ prevent table triggering a FULL load

Michael_Litz — Fri, 03 Jun 2022 14:40:54 GMT

Replicate, Transformation, Prevent Reload, Advanced Run,

Re: Adding a transform to an existing task/ prevent table triggering a FULL load

RichardP — Sat, 28 May 2022 00:13:30 GMT

The popup describes an "Apply Changes Only" task. Is that a solution too or something else?

Re: Adding a transform to an existing task/ prevent table triggering a FULL load

Michael_Litz — Tue, 31 May 2022 17:17:00 GMT

Hi Richard,

Apply Changes Only in the pop up is referring to the phase of replicate task and the type of task.

Replicate task can do a Full Load phase (initial copy of the entire table from source to target) and CDC (apply changes) where the changes are read from the transaction log and applied tot he target.

The Apply Changes Only task in the pop up refers to a task with only the CDC phase enabled. In fact even a Full Load with CDC task will have the same behavior with the adding of a transformation. Which is to want to do a reload of the table - to apply the transformation to all records.

When we do the restart with timestamp we are telling the task that we want the new transformation for future records read form source logs, but we will not apply it to existing records in the target table. So that whatever the transformation does you would need to apply it manually to the existing records in the target.

Thanks,
Michael

article Adding a transform to an existing task/ prevent table triggering a FULL load in Official Support Articles

Adding a transform to an existing task/ prevent table triggering a FULL load

Re: Adding a transform to an existing task/ prevent table triggering a FULL load

Re: Adding a transform to an existing task/ prevent table triggering a FULL load