Hi,
I am facing an issue with duplicate records when using incremental load on a table that receives data via a table insert from another table in the same data area. The incremental load selection rule is based on DW_TimeStamp, and there are three PK in the target table.
The issue is that the primary key does not seem to be enforced in the target table, as I am getting duplicate rows in the table.
I tested this with another table where data is inserted through a table insert (but without incremental load), and I still see duplicate values for the PK fields and despite setting the table option to "Use instance setting (error)", no error is thrown when duplicates occur.
I have tested this behavior in TDI 6935.1 and 6926.1, and the issue persists.
My questions are:
-
How do primary keys work with table inserts? Should they prevent duplicates, or do they not function as expected when using table inserts?
-
Can incremental load be achieved using table inserts? If so, what are the necessary configurations to ensure that primary key constraints are respected and duplicates do not occur?
Any insights, guidance, or best practices would be greatly appreciated. Thanks in advance for your help!
Best regards,
Leo
