Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
wherewasi
Starting Member
3 Posts |
 Posted - 2003-01-28 : 11:45:36
|
| Hi,I have transactional replication set up between two machines. This has worked in the past.We are up to SP3 on SQL 2000 , btw.We had to break replication to move a changed stored procedure over. The SP in question is not an article on replication.All of a sudden , I'm getting these Errors like Violation of PRIMARY KEY constraint 'PK__@snapshot_seqnos__3172400D'. Cannot insert duplicate key in object '#307E1BD4'.(Source: EPIQSQL2K2 (Data source); Error number: 2627) I read what's on MSDN and made changes to a couple of tables that had Nulls as part of a Unique Index. But this did not help. How do I begin to debug this?Thanks,Tom |
|
|
JamesH
Posting Yak Master
149 Posts |
Posted - 2003-01-29 : 07:26:28
|
| Sounds like you're doing Transactional with immediate updating. I would suggest that you ensure that you have the publisher drop and recreate all objects on the subscriber side first. If not, then replication is trying to re-insert the data that is already on the subscriber side and blowing up when it hits your PK constraint. If you can, just drop all of your replicated objects on the subscriber side and re-start your process again. Hope this helps,JamesH. |
 |
|
|
|
|
|
Replication