all groups > sql server replication > july 2007 >
You're in the

sql server replication

group:

Merge replication (SQL 2005) - could not propagate update do subscriber



Merge replication (SQL 2005) - could not propagate update do subscriber cbgoog.v NO[at]SPAM gmail.com
7/6/2007 10:48:22 AM
sql server replication: Hello,
I've got merge replication between 2 databases on the same server (MS
SQL 2005 Std), every session ends with message: The merge process is
retrying a failed operation made to article 'CLIENT' - Reason: 'String
or binary data would be truncated.'
Conflict viewer shows one row, rows seems like idetical (except one
not important field).
How to remove manually replication command to avoid waiting for
session error (sessions waits for error reporting, so changes are
replicatied with delay)?
I can reinitalize subscription and make new snapshot, but it's hard to
effect because db at subscriber is replicated (transactional) to other
server.
Thx for advice.
Chris
Re: Merge replication (SQL 2005) - could not propagate update do subscriber Hilary Cotter
7/9/2007 8:58:08 AM
Locate the guid in msmerge_contents and delete it.

--
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]

AddThis Social Bookmark Button