Merge Replication Question

In merge replication I know that it uses queuing, and I
tested it by disabling the SQLAgent at the subscriber for
awhile and updating at the publisher, then restarted the
SQLAgent at the subscriber and the data downloaded to the
subscriber from the publisher correctly. My question is:
What happens if the Publisher machine goes down (offline)
and the subscriber is still updating? Does it get queued
at the subscriber and then when the publisher comes back
online the data gets uploaded to the publisher machine?
yes it is queued or stored in metadata tables. When the merge agent runs it
determines what is new and merges it with the publisher and vice versa.
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
"Jim" <anonymous@.discussions.microsoft.com> wrote in message
news:19cc01c51e74$f559f480$a501280a@.phx.gbl...
> In merge replication I know that it uses queuing, and I
> tested it by disabling the SQLAgent at the subscriber for
> awhile and updating at the publisher, then restarted the
> SQLAgent at the subscriber and the data downloaded to the
> subscriber from the publisher correctly. My question is:
> What happens if the Publisher machine goes down (offline)
> and the subscriber is still updating? Does it get queued
> at the subscriber and then when the publisher comes back
> online the data gets uploaded to the publisher machine?
sql