migration 2000 -> 2008 with the ability to rollback

  • my task is migration from sql 2000 to sql 2008.

    I need to organize the ability to rollback after migration.

    I cannot find a standart tool and see only one way to do it by using replication.

    Tell me please what other variants are available?

    Database has comlicated logic and about 30 Gb data volume

  • Microsoft provides the Upgrade Advisor which helps you to analyse the process and possible impact of upgrade.



    There are various articles published by Microsoft under How-To topics which coveres the database migration and maintenance processes.



  • Thanks for reply

    But that is not exactly what I need.

    I have performed different finctional tests and used Upgrade Advisor.

    The problems will be able to ocure in the process of running migrated system.

    But data loss even for an hour is unacceplable for me. I need in insurance against this scenario.

    I want to have two actual systems:

    - The new system with users

    - The old system with actual (or almost actual) data

    and ability to switch users to old version in case of problem

  • This will require the build the new server and then apply a copy of current database and then setup up a transaction log shipment process untill both the databases are in sync.

    It will be a good idea to have the applicated tested in new SQL Server 2008 in test environment with no defects reported.

    But I am afraid if you can migrate the Transaction Log backup / Replication process back to SQL 2000 from SQL Server 2008.

  • That is true, log shipping from 2008 to 2000 is impossable.

    I am thinking about transactional replication. What do you think about it? Is anybody using transactional replication for such purposes?

  • This can be a work around like. Yes it can be configured to have replication configured between SQL Server 2000 and SQL Server 2008.

    When you replicate between or among different versions of SQL Server, you are usually limited to the functionality of the earliest version used. For example, if you upgrade a Distributor to an instance of SQL Server 2008, but you have a Publisher that is running an instance of SQL Server 2005 and a Subscriber that is running an instance of SQL Server 2000, you are limited to the general functionality and replication functionality of SQL Server 2000.

    Read this article for detailed information:


    I have not come accross any such situation in past.

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

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