December 13, 2006 at 1:09 am
Hello everyone,
I am replicating data from one server to other.
For the time being
I have one publisher (assumed as centralized server) containing lot of data (e.g. 15 records)
And two subscribers (assumed as booth1 and booth2) containing small amount of data (5 records each)
(No matter which one is MSDE and SQL Server all three are general servers)
I am using merger replication that has to synchronize all new changes made any where
What is happening now?
When I started replication all the records residing on publisher (15 records) transferred to each subscriber overwriting their own records.
Now each subscriber is having 15 records instead of having their own 5 records
This is problem number 1, this should not happen
Both subscribers are in continuous synchronization mode with publisher,
Records updated at subscriber 1 is transferred to publisher, that is ok no problem
But as subscriber 2 is synchronizing with publisher it will receive the recent changes made on the publisher, that should not happen,
That is problem number 2
Now if I delete some record from subscriber 1 it is being deleted from publisher and subscriber 2
This is problem number 3, it should not happen
Records should only be deleted from subscriber and not from others
plz reply me
December 14, 2006 at 5:21 am
Basically, that's what merge replication does. When a change is made at subscriber or publisher these changes will be merged so that all data is the same, barring row-filters which may be set up. Even while subscribers are syncrhonizing the changes are still tracked at the publisher and will be applied.
December 14, 2006 at 3:27 pm
>> it should not happen
You keep using that word. I do not think it means what you think it means.
Tell us what you are trying to accomplish, and we'll see if we can help. It sounds liek what you want is to have multiple publishers publishing to a single subscriber or partitioned replication so that each subscriber only gets specific data replicated to it.
December 19, 2006 at 4:02 am
Replication is typically used to keep sites synchronised. It does appear to suit what you are trying to achieve.
Perhaps you might look at some custom DTS job
Just a thought
Graeme
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply