August 15, 2005 at 9:24 am
We're getting irregularly periodic issues where transactional replication fails in the distribution agent with an an apparent primary key violation along the lines of:
Violation of PRIMARY KEY constraint 'PK__@snapshot_seqnos__5F40DF86'. Cannot insert duplicate key in object '#5E4CBB4D'.
The error doesn't make much sense given that replicated data should, by definition, have no primary key issues. I've checked the source data and have confirmed that the data is clean.
I'm also at a loss as to how I should diagnose this. Is there a way that I can translate the object it's giving me into an actual database object, or a way that I can reference that odd PK listing to a real primary key? As it is, I'm not even sure which article is the source of the problem.
Any suggestions will be welcome.
August 15, 2005 at 9:40 am
I don't think its a PK issue on the actual replicated tabeles but a bug that is described in this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;813494
August 15, 2005 at 10:01 am
Thanks! I checked our version and it does look like that might, in fact, be the case.
I'll see about applying the hotfix and see if that fixes the issue.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply