Since implementing SP3 for SQL2000, each time we change
something on an existing and fully operational replication
article (ie. add an extra column) and we try to push the
article to a subscriber we always get the error
Violation of PRIMARY KEY
constraint 'PK__@snapshot_seqnos__5B88818D'. Cannot insert
duplicate key in object '#5A945D54'. Error number 2627.
We tried this on 2 completely independent Publisher
databases and on 10+ completely independent subscriber
databases, all the same effect.
Solution now is to create a fake snapshot, but regarding
the heavy maintanance on these articles it's not the ideal
situation.
Does someone ever experienced this problem ?
Regards,
Willem van Rooij
4 Business Software
Belgium
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Willem van Rooij" <w...@4bs.com> wrote in message
news:0ec101c334c8$3216bb80$a401...@phx.gbl...