Deleting Rows from Publisher and from Subscriber

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello

I have an issue on Deleting rows on Publisher.

I want to keep a 2 months old transaction data both on my Publisher
and on the Subscribers as well,
so eatch night a process is run on the publisher that deletes 2 months
old data, so actually eatch night
I have a deletion of 1 days data (the 61st day).

Now the problem is that the next day, in the morning synchronisation,
eatch of my subscriber gets about 100.000 or even more deletions and
that makes synchronization slow.Although i have filters on my
replication,somehow deletions are send to all subscribers!!!

Now I am looking for solutions!!!

One thought of mine is to delete 2 months old transactions from eatch
subscriber, but because some subscribers share data then I belive that
if a deletion occured in a subscriber then when it synchronises the
deletion is passed to the publisher and then this deletion again is
going to be transfered to other subscribers when they try to
syncronise after.Am I right? So the issue will still be an issue.

Any Ideas of how to delete records in my case???

Please help!

.

Relevant Pages

  • Re: Deletions on Filtered tables
    ... exchangetype to downloadonly. ... I have noticed that if I have a joined filter on one table and then I ... Synchronize,the other subscribers get this row as a deletion when they ...
    (microsoft.public.sqlserver.replication)
  • Deletions on Filtered tables
    ... I have noticed that if I have a joined filter on one table and then I ... Synchronize,the other subscribers get this row as a deletion when they ...
    (microsoft.public.sqlserver.replication)
  • Re: Behaviour of Merge Replication
    ... So the branch office should be the publisher, ... would you still use a Transactional Replication after knowing this? ... I normally use pull for over 10 subscribers. ... For the merge publications use central publisher in your head office. ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge or Trans with QUS best when publishing partitions of database to slow subscribers
    ... With queued replication the single queue does serve all subscribers. ... No real conflict detection and resolution. ... The majority of the DML should originate on the publisher. ...
    (microsoft.public.sqlserver.replication)
  • Re: Identity values is checnges by initial snapshot
    ... > identities independent of the publisher, I placed DBCC CheckIdent(table, ... snapshot seed is changed to "max value + 1". ... in merge replication - if you have publisher and two subscribers, ...
    (microsoft.public.sqlserver.replication)