> Using transactionl replication to replicate data to our reporting server.
> The distributor agent is running on the subscriber. Concerned that if for
> some reason the distributor agent is down or out of service replication
> changes to the live data will not be replicated to the reports database.
> Can anyone confirm this? If this is the case then moving the distributor
> to
> the publisher would be the fix

"Hilary Cotter" wrote:

> That is correct, the distribution agent carries the changes from the
> distribution database to the subscriber database.
>
> I am not exactly sure what your concern is here. If it goes down the changes
> will remain in the distribution database until the agent starts up again.
>
> If you need to ensure your data is always replicating you will need to
> monitor your distribution agents for failures and be very proactive to agent
> failures.
>
> --
> 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
>
> "Michael Haskell" <MichaelHaskell@discussions.microsoft.com> wrote in
> message news:D2BC5733-073C-45AC-85D5-085F3D15A8DE@microsoft.com...
> > Using transactionl replication to replicate data to our reporting server.
> > The distributor agent is running on the subscriber. Concerned that if for
> > some reason the distributor agent is down or out of service replication
> > changes to the live data will not be replicated to the reports database.
> > Can anyone confirm this? If this is the case then moving the distributor
> > to
> > the publisher would be the fix
>
>