July 13, 2005 at 10:36 pm
We are using SQL Server 2000. I have setup transactional replication between our production boxs(2) a month ago. And tested works fine. And suddenly 2 days before the replication stop working and throws error duplicate key found at the subscriber(!!@#??). At the subscriber box for a particular table we found a duplicate record. But the schema is same as the publisher end.Deleted the duplicate data and now transactional replication works fine.
But I like to find out how the Key Duplicate occured. Is there any utility like Trace on/off (So that it records whether the Primary key is disables by a user)mechanism to find out in future not to happen.
July 18, 2005 at 8:00 am
This was removed by the editor as SPAM
July 18, 2005 at 12:57 pm
You're sure duplicates are not allowed at the publisher ?
July 20, 2005 at 2:56 am
Yes am sure. Primary Key is set for the column.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply