I currently have a task running that is replicating data from Dynamics AX to our staging database where we store our replica of Dynamics AX. I need to add 2 or more tables to this task and want to ensure I do this without effecting the exsiting tables that are currently being replicated. From what I understand I need to stop the task, add the tables needed, and then start the task again. How will replicate know that the new tables need an initial/full load first followed by change processing? I also wonder how/if when stopping the task that the existing table changes are still stored somewhere and not missed in the process. My assumption is that the changes will still be stored even when the task is stopped and then changes will be applied once the task is started again.
Thanks for reaching out to Qlik product community forum.
Yes, you are right in order to add new table to the existing task you should stop the replicate task. When you stop the replicate task it will store the last saved stream position (LSN/SCN) locally on replicate server. When you resume the task, it will start from where it has been stopped, so there is no way of losing the data.
When you add the new table to existing task it will set full load flag for those newly added tables and when you resume only those table will go for initial load and rest of the existing tables will go for CDC.
