September 28, 2009 at 1:56 pm
Violation of PRIMARY KEY constraint 'XPKMDT_OPERATING_MODE'. Cannot insert duplicate key in object 'MDT_OPERATING_MODE'.
(Source: TMInfo (Data source); Error number: 2627)
Is there a process to diagnose this issue? I'm a very new dba.
Thanks,
Dave
October 1, 2009 at 7:47 am
What kind of replication is this?
-Roy
October 30, 2009 at 7:56 pm
If you have access to the SQL 2005 tools you could start a profiler trace against the database on that server. I believe 2000 also has a profiler tool as well, but I have never used it, so I am not sure how similar it is, but I am sure others on the site can attest for it. Anyway, a trace should show you what SQL statements are being sent to the database and what values are trying to be input. I would imagine you could compare that to the destination table and determine your source of conflict.
Joie Andrew
"Since 1982"
November 2, 2009 at 6:11 am
There is a profiler in SQL 2000 as well. The error indicates that the row the transaction replication is trying to insert already exist. You have to identify the row that it is trying to insert. Check this command sp_replcmds. This should give you the details of all commands it has to replicate.
-Roy
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply