Post reply

Service pack 4 on replicated SQL 2000 server

  • January 15, 2007 at 8:02 am

    #67969

    Hi, I am about to install SQL service pack 4 on a SQL 2000 server that is replicating data to three other servers.  My question/concern is do I need to install the service pack on all the servers at the same time, or can I deal with the publisher first and then upgrade the subscribers at a later date.  I have read the microsoft article "Service pack 4 for microsoft sql server 2000 database components", but could do with a little clarification (I had convinced myself that the servers could be dealt with independantly, but I am now having doubts).

  • January 16, 2007 at 12:03 am

    #683401

    Upgrade sequence should be Distributor, publisher and subscriber...

    Upgrade first distributor and publisher...if you don't have time you can upgrade subscriber later for one way trans. replication but it is advisable to update all in the same window...

    The following info is from SP readme file...

    Installing SP4 on a Server that Acts as a Publisher and a Subscriber

    You might need to quiesce the system (stop all updates) and upgrade all servers simultaneously in the following cases.

    • For replication topologies based on merge replication
    • For replication topologies based on transactional replication, which updates Subscribers, including one or more servers that act as both a Subscriber and a Publisher (or Distributor).

    Example 1: Topology That Requires Simultaneous Upgrades

    The following table includes servers that both publish and subscribe to publications that allow updates at the Subscriber. As noted earlier, you must follow the upgrade order Distributor, Publisher, Subscriber for topologies that allow updates at the Subscriber. This order requires that you upgrade Server A first for the merge publication and Server B first for the transactional publication with updating Subscribers. In this case, you must quiesce the system and upgrade the servers simultaneously.

    Server AServer B
    Publisher/Distributor for merge replicationSubscriber for merge replication
    Subscriber for transactional replication with updatingPublisher/Distributor for transactional replication with updating
    Example 2: Topology That Allows Sequential Upgrades

    In this example, you can upgrade Server A first because the read-only transactional publication allows a Subscriber to be upgraded before the Publisher/Distributor.

    Server AServer B
    Publisher/Distributor for merge replicationSubscriber for merge replication
    Subscriber for read-only transactional replicationPublisher/Distributor for read-only transactional replication

    MohammedU
    Microsoft SQL Server MVP

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply