Two things. First, it's transactional replication, not merge. Sorry for
to restart the replication manually.
"Hilary Cotter" wrote:
> Not until I removed some publications.
>
> --
> 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 >
>
>
> "SQLdba" <burt_king@yahoo.com> wrote in message
> news:E20EC89D-A27E-4C0A-9B2F-4311220DFDDF@microsoft.com...
> > They run on the publisher. When you say everything would disappear, did
> > it
> > ever come back?
> >
> >
> > "Hilary Cotter" wrote:
> >
> >> There was a set of conditions which would cause the replication agents to
> >> disappear. Basically if you restored a published database, and then
> >> create a
> >> publication with the same name as the old one, everything would
> >> disappear.
> >>
> >> By chance, where are the agents running? On the subscriber or publisher?
> >>
> >> --
> >> 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 > >>
> >>
> >>
> >> "SQLdba" <burt_king@yahoo.com> wrote in message
> >> news:770297FF-ADE0-46FA-A235-93D0007C62BC@microsoft.com...
> >> >I didn't actually see this but my customer swears:
> >> >
> >> > Merge replication subscriber sql 2000 sp3a had the jobs disappear from
> >> > the
> >> > agent for about 10 hours and the publisher said it could not connect.
> >> > This
> >> > morning the jobs are back and replication was able to be started
> >> > manually.
> >> >
> >> > Help.
> >>
> >>
> >>
>
>