all groups > sql server replication > september 2007 >
You're in the

sql server replication

group:

History retained at subscriber - msmerge_contents


History retained at subscriber - msmerge_contents Natasja
9/25/2007 8:52:03 AM
sql server replication:
Hi,

I have a sql server 2000 SP4 publisher and a sql server MSDE SP4 subscriber.
After applying the initial snaphot I can see the inserted record information
remains in the msmerge_contents table. Is this normal behaviour? Is there a
way to prevent this. Our database is approximately 800MB at the publisher,
but since so much metadata is retained at the subscriber the subscription
database is about 1,5GB in size. This is becoming a problem, after a few
synchronizations our subscription database reaches the 2GB MSDE limit. Is
there any way of solving this besides lowering the retention period?
Is this behaviour different in SQL Server 2005?
--
Re: History retained at subscriber - msmerge_contents Hilary Cotter
9/27/2007 12:00:00 AM
Isn't there a 4 Gig limit and not a 2 Gig limit.

I suggest you drop your retention period from the default of 14 days to
perhaps 3-5 days.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

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]

Re: History retained at subscriber - msmerge_contents Natasja
9/27/2007 1:58:02 PM
Hi,

No the 4GB is for SQL Express, MSDE is limited at 2GB.
Lowering the retention period is not an option because the users cannot
replicate very often and we cannot risk loosing data.

But for now the problem is solved. Apparently this only happens when you use
dynamic filtering in merge replication. We removed all filters and now the
database at the subscriber is about 700MB after applying the initial snapshot
and synchronization is also much faster.

So problem solved :-)
--
Natasja


[quoted text, click to view]
AddThis Social Bookmark Button