metadata performance issue

Question

Any idea ? Why the following table grow very fast ? and what are the available configurations for a merge publication so it will less metadata as much as possible.

MSmerge_contents

MSmerge_genhistory

MSmerge_generation_partition_mappings

MSmerge_past_partition_mappings

MSmerge_current_partition_mappings

Answer 1

Hi Abdo,

An insert or update is logged into MSmerge_contents, while a delete is logged to MSmerge_tombstone.

The MSmerge_history table contains history rows with detailed descriptions of the outcomes of previous Merge Agent job sessions. This table contains one row for each line of agent output. This table is used in the distribution database and in each subscription database.

The MSmerge_generation_partition_mappings table is used to track changes to partitions in a merge publication. This table is stored in the publication and scubscription databases.

They are all by design. Please refer to Merge Replication Capacity Planning:  http://blogs.msdn.com/b/repltalk/archive/2010/06/28/merge-replication-capacity-planning.aspx.

Thanks.

---

Maggie Luo
TechNet Community Support

Answer 2

The only setting you can use to minimize the size of these tables is to decrease your publication retention time.

---

looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941