December 29, 2008 at 8:19 am
Scenario: SQL 2000 1 publisher (Merge and Trans), two subscribers.
Problem: Subscription expiration for Merge Publication set to 'never expire' hence MSMerge_contents = 44million rows. MSmerge_genhistory = 9 million rows
When pushing out to new subscriber this is causing a)snapshot to fail b)in the rare instance when snapshot works it is causing Merge push to fail as Subscriber tran log blowing up or timeouts.
Resolution: Need to delete all data upto last 7 days in the metadata tables
Question: how? 🙁
What i have been attempting is by gradully reducing the Subscription expiration in order for the automatic metadatretentioncleanup SP to do its thing (merge agent set to run every minute). Only problem is that I am currently at day 710 and at this rate I will be hear until 2010. If I decrease by only 5 days the whole thing takes ages casuing locking and other issues to end users who directly hit the publisher.
I have investigted this option
http://talatnauman.blogspot.com/2008/06/purging-merge-replication-history.html
to manully delete the data in the two table bit by bit. Any opnions on this, could it mess up replication?
Many thanks for your answers
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply