September 4, 2006 at 4:13 am
We are experiencing an issue with Merge replication in a SQL 2000 to SQL CE 2.0 scenario.
The issue relates to getting an excessive number of deletes being sent to each subscriber based on changes made by other subscribers.
For instance, the following applies
each user has access to all the organisations available.
However, they are only assigned n number of organisations at any one time.
For each organisation, there are associated clients.
Clients can be transferred from one organisation to another and that organisation does not have to be one of the ones assigned to the user.
If the client is assigned to an organisation that is not part of the users assigned organisations, that client and is associated data are now out of partition for that user.
What is occurring when other users synchronise, is that they are receiving deletes for that client and its associated data.
We have tried
One publication for all users, dynamic filtering = true, keep partition changes = true
One publication for each user (suser_sname()), dynamic filtering = true, keep partition changes = true
One publication for each user (user name hard coded for each publication), dynamic filtering = false, keep partition changes = true
One publication for each user (user name hard coded for each publication), dynamic filtering = false, keep partition changes = false
In each scenario we get the same results.
We have worked out that these deletes do NOT come from MSmerge_tombstone as they are not real deletes. This means that something else must be happening in MSmerge_contents that is causing the server to evaluate the every other user must receive information about every move of data out of one partition and into another.
We would appreciate hearing from anyone who has experienced and overcome this behaviour or form anyone who thinks they might be able to point us in a direction we are yet to try.
September 5, 2006 at 10:05 pm
check out the following
1. Some business rules part of the stored procedures where the deletes are happening, requires review
2. As a workaround try restoring a latest copy of the replicated database and check "keep existing data" option while setting up of the replication with the SQL CE.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply