Replication & Patch Installation

I have transactional replication running continously from one
publisher/distributor server to two subscriber servers. (Windows 2000
servers, fully patched and fully SP'd.)
I have experienced a problem with one of the subscriptions when taking the
publisher server off-line for patch installation, the subscriber reports a
failure to connect and then stops working.
I was wondering whether anybody has any recommendations or can point me in
the direction of best practices for taking the various parts of the
replication topology offline for maintenance
I take it you have a pull subscription?
The correct order is update the distributor, publisher and then the
subscriber. If your distributor/publisher is on the same machine, update the
publisher/distributor and then the subscriber.
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
"Nick Corlett" <Nick Corlett@.discussions.microsoft.com> wrote in message
news:09285AEC-E9B2-4CA8-8586-EEBFB408E8AB@.microsoft.com...
> I have transactional replication running continously from one
> publisher/distributor server to two subscriber servers. (Windows 2000
> servers, fully patched and fully SP'd.)
> I have experienced a problem with one of the subscriptions when taking the
> publisher server off-line for patch installation, the subscriber reports
a
> failure to connect and then stops working.
> I was wondering whether anybody has any recommendations or can point me in
> the direction of best practices for taking the various parts of the
> replication topology offline for maintenance
|||Thanks,
I do have pull subscriptions.
How about just general maintenance? Should I be worried about stopping
replication before taking servers offline?
"Hilary Cotter" wrote:

> I take it you have a pull subscription?
> The correct order is update the distributor, publisher and then the
> subscriber. If your distributor/publisher is on the same machine, update the
> publisher/distributor and then the subscriber.
> --
> 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
> "Nick Corlett" <Nick Corlett@.discussions.microsoft.com> wrote in message
> news:09285AEC-E9B2-4CA8-8586-EEBFB408E8AB@.microsoft.com...
> a
>
>
|||I think I may be missing the point here. The patches from windowsupdate
should not interfere with replication. If you get a hotfix from ms, you
should follow the ordering I outlined unless they tell you otherwise. It
would probably be a good idea to ask them.
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
"Nick Corlett" <NickCorlett@.discussions.microsoft.com> wrote in message
news:85AC3795-1CCF-4FDD-8E9F-A9358F34BB75@.microsoft.com...[vbcol=seagreen]
> Thanks,
> I do have pull subscriptions.
> How about just general maintenance? Should I be worried about stopping
> replication before taking servers offline?
> "Hilary Cotter" wrote:
the[vbcol=seagreen]
the[vbcol=seagreen]
reports[vbcol=seagreen]
me in[vbcol=seagreen]