The row was not found at the Subscriber when applying the replicated command. -- sql server replication

Hilary Cotter
2/7/2007 11:50:52 AM

Enable logging to determine which row is missing and why?

Evaluate whether the continue on data consistency error profile will work
for you here. In this case it will skip the error and continue replicating,
but your database may get progressively out of sync.

--
Hilary Cotter

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

[quoted text, click to view]

Krisnamourt via SQLMonster.com
2/7/2007 4:00:42 PM

I have Scene Replication with Central Subscriber with many Publication with
same tables. All tables have horizontal partition data about Publisher table
to Subscriber tabler. That's ok.
So, when I tried to propagated the second Snapshot of the onother publisher,
this message appear.
I read Paul Ibson article, but I canÂ´t find what step about system table I
need to clear or something like that.

I think that Distribution CleanUp Job is the guy. I just delete this Job to
never happned again, but I need to correct this quickly.

Anybody has the "follow rules" to correct this without reinitiate all
snapshot, etc, etc...etc.

Thanks .

Krisnamourt

--
Message posted via http://www.sqlmonster.com

sql server replication : The row was not found at the Subscriber when applying the replicated command.