December 4, 2010 at 4:19 am
Hi
We have 2 servers with 2005 merge replication setup and we have some questions about it:
1.) The database grew up about 55GB data(since most of them are binary image data) and log alternatively and we want to change from Full recovery mode to Simple recovery mode to reduce log size. Do we need to drop and create replication again or simply change the recovery mode is enough? Any other procedures we need to follow?
2.) The snapshot(run once about 2 weeks) job run about 3 to 4 hours. As this job drew all the resources while it's riunning and severely affect other transactions, we want to reduce it's running time. How about rebuild the index for replication system tables(e.g. msmerge_content) and how much gain by this action? Any other suggestions?
Thanks and regards,
Wallace
December 4, 2010 at 7:26 am
1. Replication won't be affected by the recovery model, but I strongly recommend to use Full Recovery and set up proper log backups to manage the log size at an acceptable size.
2. We have put the publisher and distributor on separate servers. The distribution agents use a lot of memory (at least in our environment) so if you have the distributor and the publisher on the same server, there is a great chance that there will be issues (like paging) due to low memory. In addition, no users logs on to out publisher. It's only job is to be, well, a publisher. All our users access subscribers.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply