Groups | Blog | Home
all groups > sql server replication > may 2005 >

sql server replication : Merge replication issues



llihp
5/19/2005 4:43:30 PM
We are getting a conflict error message "cannot synchronize, row was updated
outside of replication".

We cannot figure out what is causing this.

Can having different foreign key constraints at a publisher and subscriber
level cause problems with merge replication?

Sorry for the lack of information, but hopefully someone can help! :)

Earl
5/19/2005 10:03:44 PM
I have not seen that error message, but based upon my own limited
experiences, I can assure you that different constraints could certainly
create issues.

[quoted text, click to view]

Hilary Cotter
5/19/2005 11:57:19 PM
perhaps the row was updated by a process which did not trigger the triggers,
i.e. bcp, dts.

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

llihp
5/20/2005 12:00:00 AM

[quoted text, click to view]

I'm not sure what bcp is(?), but we aren't using any DTS packages within the
application.

Basically we are running a VB application at the sites, and this is
manipulating all the data within the database which is then susposed to be
sent back to the central server. We are having no issues with inserted rows
being replicated, it is only updates which are proving problematic.

Vikas Kohli
7/31/2005 9:14:01 PM
Hi,

I am also getting the same error. I have multiple publishers with a central
subscriber ( using merge property -exchangetype 2). Please let me know if
there is any answere to it.

One stange thing that I have noticed is following:

I have Publications on Same Articles at 4 sites . Some articles have 4
insert, 4 update and 4 delete triggers but some articles get only 1 trigger
for update, 1 for delete and 1 for insert. Why is this so?

[quoted text, click to view]
Hilary Cotter
8/1/2005 6:36:49 AM
Are all the triggers replication related? There should only be one trigger.
You might need to regenerate and resend your snapshot.

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

AddThis Social Bookmark Button