tag:blogger.com,1999:blog-92377218009570869.post3490343680557734416..comments2023-04-20T21:35:59.166+08:00Comments on Microsoft technologies and what I do for fun: Fixing PRIMARY KEY constraint issues in SQL Server 2005 ReplicationEdwin Sarmientohttp://www.blogger.com/profile/07565782661284058863noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-92377218009570869.post-33236914712987865052011-11-02T03:11:28.153+08:002011-11-02T03:11:28.153+08:00For the fix for "Edwin Yosorahardjo" wit...For the fix for "Edwin Yosorahardjo" with his primary key violation. It might be caused by triggers firing on the subscriber database. This is what was occuring for meUnknownhttps://www.blogger.com/profile/00159392796899599326noreply@blogger.comtag:blogger.com,1999:blog-92377218009570869.post-61135237353410629272011-06-10T08:07:35.203+08:002011-06-10T08:07:35.203+08:00In my case:
- I got 2000 db hosted in SQL 2005 sta...In my case:<br />- I got 2000 db hosted in SQL 2005 standard<br />- I change the database version to 2005<br />- setup a Transactional Replication from SRV1 to SRV2 (only insert and update, do not deliver delete)<br />- snapshot replicated succesfully<br />- transaction failed due to Primary key constraint violation<br /><br />I found that the update statement is never used, the transactions transfered are using delete and insert statements.Edwin Yosorahardjohttps://www.blogger.com/profile/09801366664837795754noreply@blogger.comtag:blogger.com,1999:blog-92377218009570869.post-83322719277339115202009-10-07T02:35:57.925+08:002009-10-07T02:35:57.925+08:00Any idea what causes this problem in the first pla...Any idea what causes this problem in the first place?Anonymousnoreply@blogger.com