Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Replication (2005)
 SQL Server Data Validation

Author  Topic 

adelkh
Starting Member

8 Posts

Posted - 2008-03-18 : 17:12:18
Hi.

I have one question regarding SQL Server replication.

I have setup SQLServer merge replication at my work, one of our subscriptions has unreliable connection to the publisher, after setting up the replication to this subscriber, it happened once that the connection was really bad so the merge agent for this subscription was failing before synchronizing data changes, and after that , the connection went good & the merge agent completed the synchronization successfully.

After a while I decided to validate all subscriptions, I discovered that this subscription has different row count for many articles although the merge agent was finishing all synchronizations successfully!!

so my question is:

how could this happen? I mean finishing the sync with success and still have different records!!

I thought that SQL Server will keep make the sync fail just because it can't do it!!

Is it right or there is something I misunderstood here?

How can I prevent this from happening again? at least I want SQL Server to inform me by failing the merge agent synchronizations.

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-03-18 : 17:23:37
Did you check Replication monitor and jobs for replication?

This will help:

http://msdn2.microsoft.com/en-us/library/ms151251.aspx
Go to Top of Page

adelkh
Starting Member

8 Posts

Posted - 2008-03-18 : 17:32:53
Thanks for your reply.
yes off course I validated the subscriber, that is how I knew that there is something wrong ( the row count is not the same) , but the merge agent was finishing the sync without errors when the connection went to good status!!
So the problem is that there were a mismatch row count between the publisher and the subscriber although the merge agent is successfully synchronizing data!!
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-03-19 : 07:47:11
How many subscribers are there for Merge Replication? Depends on Network Bandwidth issues too?
Go to Top of Page

adelkh
Starting Member

8 Posts

Posted - 2008-03-19 : 08:33:27
That Time, I only had around 10 subscribers, all have good connection except this subscriber.
Go to Top of Page

adelkh
Starting Member

8 Posts

Posted - 2008-03-22 : 03:52:11
Any more suggestions ?
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-03-22 : 16:24:25
How did you resync it? Is it one way or two way merge?
Go to Top of Page

adelkh
Starting Member

8 Posts

Posted - 2008-03-22 : 17:16:24
It is a 2 way merge.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-03-22 : 17:52:32
Looks like you need sync them manually. How did you do that first time?
Go to Top of Page

adelkh
Starting Member

8 Posts

Posted - 2008-03-23 : 03:35:33
I setup a merge replication, then added this subscriber as a push subscriber.
but why do I need to sync manually?
I need to know how this happened at the first place because I think that SQL Server should guarantee that the 2 ends are identical!!
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-03-23 : 15:48:31
>> it happened once that the connection was really bad so the merge agent for this subscription was failing before synchronizing data changes

That's why and you know it already.
Go to Top of Page

adelkh
Starting Member

8 Posts

Posted - 2008-03-23 : 16:51:48
I meant that as SQL Server should guarantee that the data is identical, this problem shouldn't have happened because ( as I think ) it should commit the transaction when it completed the sync or it should rollboack when there is a failure ( like bad connection ), but when a failure happens, it should keep giving failure message.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-03-23 : 16:57:10
Not the case if replication job stopped.
Go to Top of Page

adelkh
Starting Member

8 Posts

Posted - 2008-03-23 : 17:06:05
Thanks rmiao for your replies.
That's exactly what I need to know!!
What will happen if I just stop the merge agent during the sync , let's say after syncing half of the data?
Will it delete the synced data?
Or just keep it & skip syncing the same data when the next merge agent run happens?
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-03-23 : 19:43:51
Hard to say without looking at system. Didn't see any error in replication agents?
Go to Top of Page
   

- Advertisement -