sql server replication: Keeping merge tables small -- sql server replication

Keeping merge tables small

Chris
4/27/2006 12:32:56 PM

sql server replication: What do I need to do to replication in order to keep the merge tables
(MSMerge_contents, MSMerge_genhistory etc) as small as possible? How
significant is the subscription expiry to the size of the merge tables?

The merge cleanup job is run every day. The subscription is set to expire
after 8 days. The 3 subscribers are only likely to be unavailable for 10
mins at most.

Re: Keeping merge tables small

Hilary Cotter
4/27/2006 7:50:40 PM

On the subscriber they are pruned each time the merge agent runs. On the
publisher they are pruned when the retention period has passed. The best way
to keep them small is to lower your retention period.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

[quoted text, click to view]