question

I assume there's a front-end application has it been tested against 2008? You will need to setup replication on the new server so you can backup the databases on the 2000 instance and restore them on the 2008 instance. Setting up replication is quick and can be scripted.

I always believe that BOL and Technet are great resources for such kind of work. I said so because mostly, they have almost all kind of information you want and what steps you must take before starting the process. For instance, following are two of your interests [Considerations for Upgrading Replicated Databases][1] [Breaking Changes in SQL Server Replication][2] [1]: http://msdn.microsoft.com/en-us/library/ms143699(v=sql.105).aspx [2]: http://technet.microsoft.com/en-us/library/ms143470(v=sql.105).aspx

Thank you for the responses. I want to add a little more information and see what people recommend. Merge replication is used to keep certain database tables syncronized between two locations. The "Not For Replication" option is used and the identity ranges are different between locations. If a would configure replication on new systems, I assume that I will have to import the data into the tables at the proper sites. Meaning that I would import the data where it originated from by the identity range. The tables would then replicate and merge together as they were before the migration. Is that correct? Would it be a bad choice to replace merge replication with the database mirroring? Again, merge replication is used to keep the main and disaster recovery site data synchronized. Occasionally, data is written to our DR site and replicated to the main location. Our DR site is an active office with a large data center. Thanks.