i have been looking project side-by-side upgrade solution. suggested/used solution full of sql server 2000 database , restore on sql server 2008 norecovery. restore subsequent transaction log backups norecovery. when ready switch, change sql server 2000 read-only mode, backup tail-log , restore on sql server 2008 recovery. bring sql server 2008 online.
but, can't upgrade done transactional replication sql server 2000 publisher , sql server 2008 subscriber. script objects such logins, indexes, etc , apply sql server 2008. when ready switch, stop replication, delete replication jobs, , switch apps connect sql server 2008. haven't found suggests method. there wrong it?
the method of data migration describe possible perform using sql server replication.
there nothing wrong method or other data migration method matter, long choice decide upon addresses specific requirements of project/application platform.
that said method describe more technically involved in both configuration , implementation of actual migration steps. if can accept downtime, simple backup , restore process going more straight forward. log shipping simpler migration method.
so far, know replication method work in theory. time build out working solution in test in order validate data migration strategy , practice implementation process.
Comments
Post a Comment