March 31, 2009 at 1:23 pm
I am very new to SQL Server Replication. Now I got a problem in this area and it needs be fixed.
It is on SQL Server 2000, and Merger Replication is used for three DBs. The problem is happened in one DB about 2 weeks ago as I told. We find that the data is not sync, even in row numbers. For example, the row number in one table is 5736 in publisher side, but it is 5718 for the same table in subscriber side.
The snapshot agent (once a week) and merger agent (once every 3 min.) are running on schedule, and I could not find any error from agent history. I compared these with the design in development environment. They are the same, and data are sync between development DBs.
I have manually start snapshot agent, and then merger agent. Well, the row numbers are not change at all. It seems the replicating does not working, but no complain either. Would you please tell how to debug, and how to fix it?
Thank you sincerely in advance.
- Yelu Zhou
April 1, 2009 at 8:20 am
Have you checked for any conflicts?
April 1, 2009 at 8:33 am
yellow (3/31/2009)
I have manually start snapshot agent, and then merger agent. Well, the row numbers are not change at all. It seems the replicating does not working, but no complain either. Would you please tell how to debug, and how to fix it?
Merge replication will only replicate the changed records. So restarting the agent won't fix the problem. Is it possible that the replication was setup withoput inital synchronisation? For example if you used an backup to initalize the subscriber and when added some new records on the publisher before the subscription was setup, those records will not be synchronized.
Another possibility is that a insert conflict occured and is waiting to be resolved.
Hope this helps
[font="Verdana"]Markus Bohse[/font]
April 1, 2009 at 9:16 am
Thank you Markus!
As I was told that the replication was working till about ten days ago. It does not seems that the subscriber refreshed from its backup recently.
How to make the publisher and subscriber resynchronized?
Thank you again.
- Yelu Zhou
April 2, 2009 at 12:35 am
yellow (4/1/2009)
How to make the publisher and subscriber resynchronized?Thank you again.
- Yelu Zhou
It depends a bit on the size and number of your tables which are out of synch. What you could do is run a mock update on you table, so that the merge agent detects a change.
Something like:
UPDATE myTable
set col1 = col1
If your table is very big, it's probably better to add a WHERE clause so you only update the missing records.
This way all records in the table will be synchronized the next time the merge agent runs. But keep in mind that the missing records will cause a conflict which you might have to resolve manually. Also if you have relationships to other tables make sure all to run a update on all of them.
[font="Verdana"]Markus Bohse[/font]
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply