October 22, 2007 at 1:38 pm
Hello All, I've searched and fought with this issue for a few days now. The problem is single updates from the sub on a specific table get rolled back (conflict) by the publisher. My setup is below.
1 Publisher with 1 Subscriber
Transactional publication with updatable subscriptions, queued failover, running on a pull
publisher wins on conflicts
I have tested updating other replicated tables. Updating single records and multiple records.. all replicate fine on those tables. But trying to update a single record on this one specific table fails.. ie below statment:
update tblmain set user=2 where userid=5
However if I update multiple records in that same table it will replicate fine and not get rolled back by the conflict, ie below statement works:
update tblmain set user=2, work=0 where userid=5
Replication monitor doesnt really tell me much, It shows me the conflicts due to the failed update.. The only column that shows a difference between the two conflicts are the msrepl_tran_version.
Any help would be greatly appreciated.
October 22, 2007 at 10:35 pm
Also one other bit of info is that the update fails about 90% of the time, the other 10% it will actually update both the sub and pub without a conflit
October 29, 2007 at 11:42 am
If the table is small, try dropping the article from the publication and add it back and see if you can replicate the error.
******************
Dinakar Nethi
Life is short. Enjoy it.
******************
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply