Agent Scheduling Confusion....

I'm a little confused.
I've been working on setting up one snapshot publication for one DB, and one
"one-way" transactional publication for another DB (both on the same
server).
My three "client" subscribers are running MSDE 2000 SP3, and they are
subscribing to these to Publishers.
As I have been in the process of setting these up, I'm having difficulty
understanding how all the "scheduling" works.
I mean there's a schedule for the "snapshot" agent. a schedule for the
"transactional" agent, a schedule for the "distribution" agent, a schedule
for the "subscriber" agent, ... and so on.
For my scenario, I need to know how to configure all the schedulers
(publisher and subscribers) so that when the "client" subscriber is
connected to the network, it automatically checks to see if there is an
updated snapshot, and see if there are any "transactional" transactions
published at the publisher. I want the publisher to publish the "snapshot"
every day at 3:00 AM, and I want the "transactional" publication to always
be "up-to-date".
Any ideas on where to get the most useful information about all the
"scheduling", or should I buy a book on replication
I've become pretty much adept at the actual setting up of all the security,
folders, etc. I'm just real unsure about the scheduling of the different
agents...
Thanks
-- Will G.
When you want the subscriber to determine when to connect to the publisher
and download updates you should be using a pull subscription.
Either that or use a push subscription and schedule your distribution agent
to run every 1 minute and have it fail continually until the subscriber
connects. The first option is the better way to go.
You can schedule your pull agent to run continuously. You might want to
configure your subscription to be managed by Windows Synchronization Manager
for a greater range of options on when to pull your subscription, for
instance it can pull your subscription on logon, when the network connection
is live, etc.
If you schedule your snapshot to run every morning at 3:00 it will only be
generated the first time, and subsequent times when a subscription needs
reinitialization, ie you made a schema change or the subscription expired.
You are still probably confused. Post back with any remaining or new
questions you might have, and someone should pick them up and answer them.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Will Gillen" <gille001@.nsuok.edu> wrote in message
news:ODw6zwevEHA.3080@.TK2MSFTNGP12.phx.gbl...
> I'm a little confused.
> I've been working on setting up one snapshot publication for one DB, and
one
> "one-way" transactional publication for another DB (both on the same
> server).
> My three "client" subscribers are running MSDE 2000 SP3, and they are
> subscribing to these to Publishers.
> As I have been in the process of setting these up, I'm having difficulty
> understanding how all the "scheduling" works.
> I mean there's a schedule for the "snapshot" agent. a schedule for the
> "transactional" agent, a schedule for the "distribution" agent, a schedule
> for the "subscriber" agent, ... and so on.
> For my scenario, I need to know how to configure all the schedulers
> (publisher and subscribers) so that when the "client" subscriber is
> connected to the network, it automatically checks to see if there is an
> updated snapshot, and see if there are any "transactional" transactions
> published at the publisher. I want the publisher to publish the
"snapshot"
> every day at 3:00 AM, and I want the "transactional" publication to always
> be "up-to-date".
> Any ideas on where to get the most useful information about all the
> "scheduling", or should I buy a book on replication
> I've become pretty much adept at the actual setting up of all the
security,
> folders, etc. I'm just real unsure about the scheduling of the different
> agents...
> Thanks
> -- Will G.
>
>