Ok, I need to do two things. Move from BES 4.0.6 on a Win 2k server to 4.1 on a win 2k3 server and move the database from local MSDE to stand-alone SQL. I have instructions on moving the database, thanks to the members here, and I am wondering if I can do both of these things at once. Would this work:

1. Turn off win 2k server BES services
2. Build 2k3 server to 4.0.6 with same info as 2k server
3. Perform steps to move database from MSDE to SQL
4. Make sure the new server works, then upgrade 2k3 server to BES 4.1

Essentially, a knife-edge cutover while moving from MSDE to SQL. Would this work? Has anyone ever attempted something like this?

I'd do the upgrade first on the win2k server and then cut over to 4.1 SP4 on the new server ... but either will work.

BBAdmin might chime in with some sneaky way he thinks you should upgrade ... it requires a Snickers bar, 25 toothpicks, and a pack of gum.

I can see how that might be smoother, but I was hoping to have the old server in the original state in case any of this didn't work and I had to back out of it.

I guess I'll have to head out tomorrow and purchase some toothpicks.

Yeah either will work. Mostly that order can depend on if the old hardware you are moving from is capable of handling the new version. This was really only an issue for very small shops or people making jumps from 3.6 to 4.1.

Don't forget to use the CreateDB utility to create a new blank database of the same name on the SQL server, then do the backup and restore. If you upgrade first, use the CreateDB from 4.1, if you move then upgrade, use CreateDB from 4.0.

Also a good idea. Though if you have a backup of your database then you can always recreate your server within a few minutes. All the settings are stored in the database after all.

My reason for doing it in place and then moving is that you only have the one codebase on the new server. Performing a backup will get you the same thing; but I can certainly understand wanting to have the old server to fail back to in this case.

That's a very compelling reason to do it that way. I think you are right, having the cleanliness of only one codebase will be worth the few extra minutes it would take to restore if something went wrong.

Thanks to both of you for the advice thus far. I'll keep checking this thread until Wednesday, when our upgrade is scheduled.