UpgraSQL 7 to 2000 - any replication implications?

  • I have to write a report on the implications of upgrading SQL 7.0 to SQL 2000 when there is an existing SQL 7 replication environment set up. This might have been some time ago for most of you, but please could you reply if you had any problems/issues when upgrading.

    Paul Ibison

    Paul.Ibison@blueyonder.co.uk


    Paul Ibison
    Paul.Ibison@replicationanswers.com

  • can you tell us if SS2K is the subscriber or the publisher? if SS2K is the subscriber, no problems at all. You can accept the updates and upward compatibility covers all your woes.

    If SS2K is your publisher, you have to take additional precautions.

    As much detail about your environment as you can provide will help us help you better.

  • The report needs to take into account each possible combination, but I guess the publisher and distributor are the main concerns.

    Paul Ibison

    Paul.Ibison@blueyonder.co.uk


    Paul Ibison
    Paul.Ibison@replicationanswers.com

  • The only thing I know for sure. Distributor should be upgraded first, then publisher and then subscriber. However, SQL2K

    transactional replication supports 7.0 publisher and 2K subscriber.

    I suggest checking indepth the MSDN and MS Knowledge Base sites and around the various search engines for more detail. Then there is Google is good to search the newsgroups which offer even more possiblities.

  • Nothing to it. Antares is right about the order of upgrading. Biggest thing is once you upgrade, amend your publications to leverage concurrent snapshots and see if you can take advantage of pre/post snapshot scripts.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

Viewing 5 posts - 1 through 4 (of 4 total)

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