I have merge replication setup up for 6 SQLCE Subscribers.
I have noticed that the MSmerge_tombstone table is growing
at a fast rate regardless of any changes to the data in
the database. It seems to be consistantly adding 50 rows
of data to the table every 2 minutes. As the table grows
it causes the SQLCE subscirbers to fail with the following
SQL Server Reconciler failed: Run
: Failed to enumerate changes in the filtered
: The merge process timed out while executing a
query. Reconfigure the QueryTimeout parameter and retry
I'm sure that this is due to the size of the
Should the MSmerge_tombstone table grow at this rate?
36,000 rows every 24hrs!
I understand there is the sp_mergecleanupmetadata Stored
procedure but if i use this does that mean that because i
have to reinitialise all the subscribers, they are going
to have to pull down the whole subscription again.
I have since Changed a settings to make subscription
expiration date to 8 days instead of never expires but
we're still getting 50 rows added every 2 minutes
SQL SERVER 2000 SP3
Hope someone can shed some light on this for me.
I did try this sp last week when the table had grown to just under 1 million rows, however I was forced to reinitialise the subscriptions.
I will probably run it agian at the end of play today and then get them to resync in the morning. And then see if the change in retention has done anything.
running the sp and reinitialising on a regular basis is going to be difficult as the devices are synchronising throughout the day and I can't get them all in to upload their changes first. Plus I don't want them to download the whole subscription again. 5mb over a fairly slow link to the server.
Do you think 50 rows every 2 minutes is unusual behaviour. Or is this to be expected?