"Wingman" wrote:

> We have a SQL 2K5 with sp2 as a publisher using push replication to two other
> SQL servers. One of the subscriber servers is SQL 2005 and the other one is
> SQL 2000. I recently made a table schema change which I increased a few
> length in a field from Varchar(20) to Varchar(50). To make this schema
> change, I first removed the table from replication and made the change, then
> add the table back to the replication. Subsequently I created a snapshot and
> let the replcation start replicating the table. The replication to the SQL
> 2K5 subscriber server has no problem but the replication to SQL 2K subscriber
> has repeatedly been delivering the snapshot over and over again. As soon as
> a snapshot is done, the same snapshot of the table happens again.
>
> Let me add one more detail in this problem, while delivering the first
> snapshot to the SQL 2K subscriber, there were some 'can't insert due to
> duplicate primary key' errors in the SQL 2K subscriber database shown in the
> replication monitor. I didn't know how this would happen because the other
> SQL 2K5 subscriber has no such issue but I proceed to remove the records in
> the SQL 2K subscriber database so the repliation can insert the records.
> This cleared the dupliate primary key errors. I don't know if this woyuld
> confuse the snap agent about the status of the snapshot. In any case, the
> snapshot is still repeating as I write this email. When I look at the
> replication monitor, it has been repeated three times so far. The table is
> quite big, 5.5 million records. How can I stop this repeating snapshot
> process?
>
> Any idea on this is very much appreicated.
>