FEATURE : We are suggesting to add a feature in Qlik replicate to have the ability to control where the Cached records go during the Full load.
There should be a feature in the Qlik replicate when connecting to SQL server, after the full load completes, the Replicate should have the ability to control Cached records as to where it should go (1) BULK table only (2) CT table only (3) currently it goes into both BULK and CT causing duplicate between Bulk and CT
TASK EVENT Steps:
1. Highlight any Table in a Task
2. Click Reload
3. Say ex:Table1, If the table has 100 records, when the full load in progress, send additional 2 records
4. The 2 records (which are Cached records) goes into both the Bulk (Table1) and CT (Table1__CT)
This causes additional effort to negate the common records(2 rows in this case) between the Bulk and the __CT tables
Feature Request:
There should be a feature in Qlik replicate for us to control the Cached records from going into both the BULK and __CT tables such as (1) Cached records into BULK table only (2)Cached records into CT table only