Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQl 2005 Bidirectional Merge replication - Publisher<->Subscriber Small Data Mismatch Expand / Collapse
Author
Message
Posted Monday, February 11, 2013 12:33 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 2:56 AM
Points: 25, Visits: 268
Hi all,

Firstly SQL 2005 Bidirectional Merge Replication is setup and working between the Publisher and the subscriber.

I am monitoring the stats for Downloaded and Uploaded statements and for the most
part things are looking great.

I am doing data compares (Excluding the timestamp datatype) to confirm things are A ok and
I found that for a few records (Current count is 5) on a certain datetime column is different on the
Publisher from the Subscriber and I was hoping to track down as to the reason.

Please note
1. There are no Triggers on the Subscriber at all.
2. There are some AFTER triggers on the Table in question on the Publisher but none of them
affect the field in question.


Unsure if this helps but I have also tried to run the below to force the row in question through from the Publisher to the Subscriber but this also does not force things through for the field in question.

declare @int as int
exec @int = sp_mergedummyupdate 'customer','0DDA6892-5E59-E211-8F91-001A64DB8758'
select @int

Any advise would be greatly appreciated.

Kind regards,

Matt
Post #1418233
Posted Monday, February 11, 2013 8:33 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 2:56 AM
Points: 25, Visits: 268
FYI i have been monitoring the data on a hour to hour basis and 99.9% of the time all the data is OK but the trend

seems to be a few records per day fall into the non-convergence category in which case i manually amend the data

to bring back into convergence but I sure would like a bit of advice on a troubleshooting method for the

rows of data in question to be able to audit the replication process to identify why the change was not

pushed out to the subscriber.

Please note that we can rule out the change happening on the subscriber, this is purely an update on a row of data on

the Publisher Not Propagating to the Subscriber Regardless of the manual calls to sp_mergedummyupdate to re-push out

the rows.

Any advice\comment greatly appreciated.

Kind Regards,

Matt
Post #1418726
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse