Duplicate Records When Using Microsoft SQL As Replication Service Target
Article ID: KB0079028
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud Integration - Connect ( Scribe ) | - |
Description
If you modify the properties of an index associated with a SQL database table being used as a Target for a Replication Solution, updated records are inserted. However, the Replication Solution may be unable to delete the original records that were being updated, causing duplicate records to occur. Best practice is never to modify the properties of an index.
If you have modified an Index, the list below provides the naming convention and default settings for each type of Index:
ndx_[primary key field name]
Unique
Non-Clustered
Index key column = primary key of the entity
Index key example from Dynamics CRM Contact entity = ndx_contactid
ndx_[most recent record processed field name]
Non-Unique
Non-Clustered
Index key column = DateTime field used to determine if the record has changed since the last run of the RS Solution.
Index key example from Dynamics CRM Contact entity = ndx_modifiedon
ndx_SCRIBE_DELETEDON
Non-Unique
Non-Clustered
Index key column = SCRIBE_DELETEDON field generated by Scribe Online when creating Target tables for the RS Solution.
PK_[entity name]
Clustered
Issue/Introduction
Modifying the properties of an index associated with a SQL database table being used as a Target for a Replication Service (RS) Solution may cause duplicate records.
Resolution
If you are experiencing issues with duplicate records in your Microsoft SQL RS Target database, verify that the index properties are correct for each entity.
(D 2455, D28510)
Feedback
Yes
No
Powered by
