August 31, 2005 at 10:26 am
We are publishing a single table to two subscribers. Both subscribers get new rows in the table but only one subscriber gets updates, the other does not. Reinitializing the replication fixes the problem, but that is not what we want to do.
Any ideas why one subscriber would get updates, but the other one doesn't? We thought it may be a permissions problem, but why would the subscriber create new rows, but not save updated rows?
Thanks for any help with this one.
September 1, 2005 at 5:09 am
The reason might be logged in the conflict viewer.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
September 1, 2005 at 9:48 am
When I try viewing conflicts for the publication, I get "An unexpected error occured while trying to launch the Conflict Viewer". Any suggestions on how to fix this?
September 1, 2005 at 1:22 pm
I don't know specifically why the conflict viewer won't work, but the conflict data is stored in conflict tables in the publication DB. You can check there manually. For example: conflict_PubName_TableName.
Dylan Peters
SQL Server DBA
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply