|
Home > Archive > MS SQL Server Replication > July 2005 > Purge MSmerge_contents and MSmerge_tombstone on MSDE
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Purge MSmerge_contents and MSmerge_tombstone on MSDE
|
|
|
| I am running SP4 on server and MSDE's. Using Merge replication with anonymous
pull subscriptions.
BOL says merge_contents grows indefinately. In the How Replication Works
article under the Merge Meta Data Cleanup section, it implies cleanup of this
table would only happen manually and if you adhered to its strict
requirements. It will be unreasonable for us to expect our laptop users to
all synch at the same time. So it sounds like meta cleanup on the laptops is
out for us. However, the section vaguely talked about this table affecting
performance. Any ideas on what this performance threshold would be? Let's say
hard drive space is not an issue (I think right now our clients have 60
giggers). Is it a problem at 100,000 records? A million records?
Thanks,
Buzz
| |
| Paul Ibison 2005-07-25, 3:36 am |
| Buzz,
If the - MetadataRetentionCle
anup Merge Agent parameter is set to 1, as it is
by default, the Merge Agent automatically cleans up the Subscriber and the
Publisher that are involved in the merge. Note:
The - MetadataRetentionCle
anup 1 parameter is now part of all Merge Agent
profiles that ship with SQL Server 2000 SP1 and later.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|
|
|
|
|