RE: Snapshots, Validation, Resynchronization with Merge Replicatio
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
I meant to say "copies it down to the distributor machine"
"gopal" wrote:
> My first question is why are you reinitializing the database once every
> week? This is not necessary unless the subscription requires to be
> reinitialized.
>
> In your topology when you run the snapshot agent, it runs on the
> distributor, it makes a connection over the network to the publisher and
> bcp's out the data and copies it down to the publisher machine, thats the
> reason you see so much traffic,
>
> Here is my suggestion.
>
> 1: Check you publication retention period (in the main tab of publication
> properties), it is normally set to 14 days by default
> What this means is that a subscriber has 14 days to sync at least once
> before it is marked as expired (which is one of the main reasons you need to
> reinitialize)
>
> 2: If you can gurantee that the subscriber can sync once every 14 days then
> you dont have to worry about reinitializing (at least for this reason)
>
> NOw the question is how often do you have to run the snapshot. The snapshot
> need to be run only ONCE every retention period, that is once every 14 days,
> if the snapshot is not run once every retention period then you can get an
> error in the agent saying the snapshot is obsolete, at which time you can
> just run the snapshot agent and then start the merge agent and it will pick
> up from where it left off.
>
> To answer your question about snapshot, running the snapshot DOES NOT mean
> that you are reinitializing, we are just generating schema and data files
> along with updating some metadata. This does not result in the data being
> refreshed on the subscriber.
>
> HTH
>
> "Hugh" wrote:
>
> > Hi,
> >
> > We are running continuous merge replication on about 50 databases (sql
> > server 2000). Each database has only one subscriber, and that subscriber is
> > located across the internet and available via a VPN tunnel.
> >
> > Since the publisher server is our "live" server, I set up the distributor on
> > our subscriber server. The thought was that we didn't want to have 50
> > replmerge.exe's running on the live server.
> >
> > Originally, we set up the databases to resynchronize every weekend. The
> > problem is that the snapshot agents run on the distributor, so there is a lot
> > of bandwidth being used to create the snapshots. Then i read in this
> > newsgroup that resynchronizing of merge replications is only needed if the
> > databases don't pass validation.
> >
> > That said, here are my questions:
> >
> > Why is there so much bandwidth going from the distributor to the publisher
> > when a snapshot agent is running?
> >
> > I know I can set the snapshot agents to run on a monthly schedule, but is
> > that the same thing as resynchronizing on a monthly schedule?
> >
> > Is there a way I can get the server to alert me if a subscription is
> > invalid? I have seen the message once or twice, but it always seems to be a
> > connection issue (i.e. restarting the merge agent makes it go away).
> >
> > Sorry for being so long-winded. Thanks for the help.
> >
> > Hugh.
.
Relevant Pages
- RE: Merge pull subscription -- Applying snapshot from alternate UN
... It is actually no need to specify snapshot folder for web synchronization in your RMO program. ... it just needs to know the web synchronization path and let merge agent know where the distributor is. ... There is a direct connection from your merge agent to the snapshot and actually also a direct connection to the distributor, ...
(microsoft.public.sqlserver.replication) - Re: Snapshots, Validation, Resynchronization with Merge Replicatio
... You should have your distribution database on your ... In your topology when you run the snapshot agent, ... What this means is that a subscriber has 14 days to sync at least ... NOw the question is how often do you have to run the snapshot. ...
(microsoft.public.sqlserver.replication) - Re: Snapshot Creation
... Distributor/Publisher with my AD account (Windows administrator and SQL ... But making my AD account the owner of the Snapshot Agent job, ... Looking for a SQL Server replication book? ...
(microsoft.public.sqlserver.replication) - Re: closer, but not quite
... snapshot agent history as to whether the user defined data type was included ... The snapshot history output looks ... How do I run the script against the subscriber database? ...
(microsoft.public.sqlserver.replication) - Re: Snapshot Publication is not allowing cleanup of the distribution d
... Even though the snapshot agent is shut down, the Log Reader agent continues delivering transactions to the distribution database. ... Given that my snapshot agent runs much less frequently, the transactions that have occured since then, are being accumulated in the distribution database. ...
(microsoft.public.sqlserver.replication) |
|
