May 16, 2008 at 8:14 am
We will be migrating from our 2000 server to 2005 in the next couple of months. One of our applications I'm a bit worried about and would like to set it up in a testing environment. My goal is to keep the current version live with all of the work being done as it is now but have the 2005 server running for testing purposes. Ideally, I would like for the 2005 database to be updated from changes made in 2000 (the current application), thus my question.
I know there are a number of different replication technologies do to this. Ideally, once we prove the 2005 installation to be sound, I would like to simply turn off the replication and the 2000 server and then point the application to the 2005 server. Given the scenario, what would be the best technology use?
May 16, 2008 at 1:08 pm
well I've successfully replicated sql 2000 databases to sql 2005, subject to the conditions and restrictions of transactional replication.
So answer yup you could do what you want to do.
after tetsing you could just detatch and attach the databases, this works well too.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply