Re: Snapshots, Validation, Resynchronization with Merge Replicatio



1) The agents will be preferentially paged to the page file, so while they
will cause memory pressures it shouldn't be that bad. Also on most of my
systems I don't see replmerg consuming more than 4 Mg. You might want to
schedule them to run every 10 or so minutes to lessen the impact.

2) the snapshot files are generated on the publisher. By default they will
be deposited there instead of the distributor although you could place them
there as well.

Are the publications similar - you might want to look at dynamic snapshots
which might allow you to reduce the numbers of publications.

--
Hilary Cotter
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

"Hugh" <Hugh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:70F93366-2459-4BF7-8230-314ECB13BEDD@xxxxxxxxxxxxxxxx
Hi,
Thanks for the great replies.

We have 50 publications on Server1, and 50 subscriptions on Server2, with
the distribution database on Server2.

This means we have 50 replmerge.exe's running at all times, since we are
running continuous merge replication. Each of them takes up about 10MB of
memory, so that's 500MB of memory on a 2gb database server.

1. If the distribution database is on our publisher (Server1), then our
"live" server effectively has 500MB less RAM to work with than our
"backup"
server. Won't this affect performance? Or is there an increase in
performance from having the distributor at the publisher that makes up for
this lost 500MB of RAM that the SQL Server could be using?

I understand now about the difference between resyncing and snapshots, but
I
still have a question about it:

2. If the snapshot is a "snapshot of the publication", and the snapshot
files are located at the publisher, why do we see 10X more bandwidth going
from distributor to publisher than vice versa? Is the snapshot file being
generated from data at the publisher or at the distributor?

Thanks again for the help.

Cheers,

Hugh.






.



Relevant Pages

  • Re: Inactive Publisher??????
    ... MSdistpublishers table in msdb on the distributor server shows the ... Shouldn't the publisher server have is_publisher=1? ... I then imported data from the publisher to the subscriber so that the ...
    (microsoft.public.sqlserver.replication)
  • Re: Remote Dist - Snpsht / Trans Replication Fails to Create
    ... Has anyone created any previous publications on the publisher or ... Issue the Select @@servername query on the publisher and distributor. ... >> Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: Inactive Publisher??????
    ... The publisher name is in ALL CAPS. ... disabling distribution on the distributor and then rebooting ... made sure the other server was set up for publication. ... I then imported data from the publisher to the subscriber so that the ...
    (microsoft.public.sqlserver.replication)
  • Re: Error: 21670 SQL Server could not connect to the Distributor using the specified password. (Conf
    ... Connection to server failed. ... 2- Right click on the replication folder and select distributor ... If you have already entered your publisher ... the distrubution properties ...
    (microsoft.public.sqlserver.replication)
  • How do I "really" reinitialize a subscription?
    ... Publisher on BoxA, Distributor on BoxB and ... Subscriber on BoxC. ... subscriptions with generate new snapshot. ...
    (microsoft.public.sqlserver.replication)