Re: Apply snapshot regularly

Tech-Archive recommends: Speed Up your PC by fixing your registry

There is no point to do this unless you know you are out of sync. I would
run monthly or weekly validations to see if you are out of sync. Then if you
are reinitialize and then manually start the snapshot agent. The log reader
and distribution agents run fine when you are simultaneously generating a
snapshot.

For named subscriptions the snapshot will only be generated when you have a
new subscription, or when you have reinitialized a subscription or
subscriptions. For anonymous subscriptions a snapshot will be run each time
your snapshot agent runs.

While the snapshot agent is being run the published tables will be locked.
After the snapshot has finished the locks will be released, while the
distribution and log reader agents are running they will not hold any locks
on the published tables.



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

"Wingman" <Wingman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B03834F3-CA1F-4CC8-9A79-E59593C3CD33@xxxxxxxxxxxxxxxx
>I am planning to do a snapshot regularly once a month to make sure that the
> publshing database and subscriber database are always in sycn. Our
> system
> is 24x7 but night time and weekend are relatively quiet. Is the correct
> process for this is to do the 'Reinitialize All subscriptions' in
> Replication
> Monitor or just start the Snapshot Agents? Do I need to shut down the
> Distribution Agent and/or Log Reader Agent first before I do anyone of
> these
> options?
>
> Also, will the tables in the publishing database that are being
> transferred
> over to the subscribing server be locked by SQL server during the
> transfer?
>
> wingman


.

Relevant Pages

  • Re: Apply snapshot regularly
    ... If you run the snapshot again the snapshot will only be generated if there ... is a subscription that needs it or if you are using anonymous subscriptions. ... time your snapshot agent runs and be distributed to all of your subscribers. ... So reinitialize is saying this subscriberneeds a new snapshot and the ...
    (microsoft.public.sqlserver.replication)
  • Re: snapshot question
    ... for snapshot processing for SQL replication, I am very interested in knowing ... and apply the snapshot files from the external drive at the subscriber site. ... the snapshot agent will not do anything when it is scheduled to ... run unless there are inactive subscriptions (those that are *not* created as ...
    (microsoft.public.sqlserver.replication)
  • Re: SnapShot Agent Schedule in Merge Replication..
    ... You can configure your snapshot to run whenever and however you want. ... For named subscriptions the snapshot is generated weekly, ... > It has setup the Snapshot Agent Schedule to run Once every 1 week. ... > Can I change the snapshot agent schedule to run on Demand? ...
    (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)