05-13-2011, 12:31 PM
Join Date: May 2011
Post Thanks: 2
Thanked 0 Times in 0 Posts
| | Upgrading 4.1.7 to 5.0.3...have a DB concern
Please Login to Remove!
I been digging through searches for this, but couldn't really find an exact answer. I've been doing my research on this upgrade, have it planned out, and I have all of the documentation and tools I'll need. We only have 50 devices, but they all belong to execs who have been in a bit of a firing frenzy lately.
I'll be doing a parallel upgrade. Our servers are virtual so I'll be upgrading a copy of our original server's VM. The DB is on the server in an MSDE instance. So when I copied the server, the DB is now also on the copy. I know the upgrade process will install SQL2005 Express.
My concern is that when I finish the upgrade, the new server will try to immediately contact/take control of routing all of the devices in the DB. This is a concern because I want to be able to migrate a few users at a time, using the transporter, before fully migrating off the 4.1.7.
Should I, before the upgrade, delete the users on the copy? To make sure there is no potential confusion later on.
Or am I over-thinking this, and I'll just have to use the Transporter to effectively change the SRP configuration for the devices/profiles?