Re: Newbie question: "No replicated transactions are available"

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The log reader agent will read your transaction log and construct commands
which it writes to the distribution database. The distribution database then
reads these commands and applies them on the subscriber.

If your distribution agent is reading "no replication transactions are
available", either your log reader is not reading them in the transaction
log, it is stopped, or there are no transactions hitting your publication
database.

If you only want data updates every hour, have your distribution agent run
hourly.

The snapshot agent will generate scripts and data files which will be
applied on the subscriber. These scripts will recreate the objects you are
replicating on the subscriber, the data will make your subscriber a clone of
your publisher (with some exceptions). I hope this answers your questions,
if not please post back.

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

<mkerrigan@xxxxxxxxx> wrote in message
news:1137252443.744733.38970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> Hilary Cotter wrote:
>> With anonymous subscribers the snapshot job will be run each time it is
>> scheduled and it will generate a new snapshot. This can cause locking on
>> your publication database. With named subscribers the snapshot job will
>> be
>> run each time it is scheduled, but it will close down unless you have a
>> new
>> subscriber or require a new subscription due to a reinitialization.
>
> But I want the data updated every hour. How can it do this if the
> snapshot job is only scheduled to run once a day?
>
>> The distribution agent does not need a snapshot if you have done a no
>> sync
>> subscription. Chances are you have done a sync subscription.
>
> I guess I'm not fully understanding this process. If there is no
> snapshot, to me it seems that no data will be updated, so what is the
> distribution agent distributing? The same exact data it distributed an
> hour before? This doesn't make sense to me.
>


.

Relevant Pages

  • Re: trans replication of large tables...
    ... Yes, but I tend not to use the snapshot agent to generate the data, and the ... and put the tables into the subscriber by manual methods like ... How to setup the ?UseInprocLoader on the distributor agent so it don?t ...
    (microsoft.public.sqlserver.replication)
  • RE: Merge pull subscription -- Applying snapshot from alternate UN
    ... In one line my objective is to apply the initial snapshot from the CD or UNC ... Even if the subscriber needs to connect to web server to get some ... Using RMO to create the subscription and start the merge agent ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.replication)
  • Re: Transactional Replication Issues
    ... The process could not connect to Subscriber 'SQLServer2'. ... distribution agents will allow the snapshot agent to run (fewer processes ... Server Agent configured to run many jobs? ... configured all you replication agents to run under explicit Windows ...
    (microsoft.public.sqlserver.replication)
  • Re: Snapshot agent job roles
    ... merge and not transactional/snapshot replication. ... you'll have a merge agent at the subscriber for a pull subscription. ... controls the propagation of the snapshot when the initialization takes place, ...
    (microsoft.public.sqlserver.replication)
  • Re: Transactional Replication Issues
    ... 64bit windows, although it is a higher limit compared with 32bit Windows. ... The process could not connect to Subscriber 'SQLServer2'. ... distribution agents will allow the snapshot agent to run (fewer ... Server Agent configured to run many jobs? ...
    (microsoft.public.sqlserver.replication)