SQL Server Performance

Replication during upgrade.

Discussion in 'Performance Tuning for SQL Server Replication' started by akus, Jun 16, 2005.

  1. akus New Member

    We are upgrading a system with 2 different replication topologies (one inward and one outward).

    Topology 1 (outwards to satellites)
    SQL7 - Publisher
    SQL7 - Distributor
    SQL7 - Subscriber

    Topology 2 (inwards from satellites)
    SQL7 - Publisher/Distributor (also topology 1 subscriber)
    SQL7 - Subscriber (also topology 1 publisher)

    Because we are doing upgrade to over existing versions and SQL2000 cannot be subscriber to SQL7 Publisher/Distributor we must stop the inwards replication before topology 1 publisher is upgraded (because topology 1 publisher is also topology 2 subscriber creating the conflict).

    Does someone have experience of risks involved in this operation (or of any articles on subject). We are worried of any potetnial data loss while inwards replication is swithed off. Also is there any risk involved when upgrading from SQL7 to 2000 while replication is running?

    Thanks
  2. satya Moderator

    You must stop REPLICATION process until the upgrade process is finished, you must suspend transaction activity in the databases and suspend replication. Note that replication includes the creation and dropping of both routes and subscriptions

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page