1. Is there any issue with creating these tasks for the same source tables? If there are any concerns about creating the above tasks, could you let us know?
2. When the customer try to reload a specific table in Task A, they can select the specific table and select [Reload], and then start the Task A [Resume Processing] to reload the table.
My understanding that it is not problem, but is there any concerns or any affects to the other task or tables?
@iti-attunity-sup There will be not be any issue in terms of execution of tasks but there might chance there will be load on that source since more than one task will be extracting the data which might result on the throughput of the data.
1. Keeping Full load and change capture in a single task works seamlessly and is taken care of by QR itself.
2. if you separate the Full load and CDC in different. You have to identify the starting point of CDC and there are other options in terms of full load as well like full load stop when the initial full load done or apply the cached changes as well.
3. Full load directly interact with Source db and updates metadata in QR metadata, on the other hand, CDC interact with QR metadata and transaction/archive logs.
4. adoption of the correct term or approach is deepand upon customer use case.
If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer. if you require further assistance, please raise a Support case.
