Prev: Rube Goldberg triviality when adding rows that have non-NULL rowguid columns
Next: cannot delete publication
From: Himanshu on 11 Jul 2007 15:16
Environment: SQL 2005 - merge replication

I noticed that merge agent process is taking up 90% of my cpu - and the
culprit was sp_MSenumgenerations90. msmerge_contents and msmerge_tombstone
are not too big - only 50K records.

I have about 3 million records in the msmerge_genhistory table. The oldest
record is 14 days old. I checked for fragmentation - looks good.

So I modified my publication and set the subscription expiration to 3 days
- down from 14.

My question is - how do I enforce this change so it would cleanup the
msmerge_genhistory table. I looked at my agent profile and
-MetadataRetentionCleanup is set to 1. I restarted the Merge Agent - but to
no avail. I still have 3 million records (14 days worth) in the
msmerge_genhistory table.

What else can I do?

 | 
Pages: 1
Prev: Rube Goldberg triviality when adding rows that have non-NULL rowguid columns
Next: cannot delete publication