Upgrading from 2.0.6 to 3.1.9

daveronson · Post by **daveronson** » Wed Jun 21, 2006 7:40 am

Is it recommended to upgrade directly from 2.0.6 to 3.1.9? Approximately how long should I anticipate the upgrade of the server to take? The database is approximately 3 GB.

dan · Post by **dan** » Wed Jun 21, 2006 8:31 am

You should be able to upgrade directly from 2.0.6 to 3.1.9. However, since the 3.1 release required some database structure changes, the upgrade could take awhile, but it is hard to predict how long, because it depends on the structure of your DB. It could take minutes or hours, but 3GB is not terribly big, so it seems unlikely to take hours.

If you need to know ahead of time, you could copy your database to a different machine and run the upgrade there to see how long it takes.

Either way, definitely make a copy of the database prior to the upgrade.

daveronson · Post by **daveronson** » Wed Jun 21, 2006 9:06 am

That's a good idea. Is it possible to do the whole upgrade, license keys and all, in a sandbox environment so I can fully document the process?

dan · Post by **dan** » Wed Jun 21, 2006 9:21 am

Yes, the whole upgrade would be the recommended way to do this. You can always login as admin locally, so you don't really need to worry about licenses. Suggested steps:

1. Move Vault DB to test machine
2. Install 2.0.6 on test machine, choosing to keep DB
3. Install 3.1.8 on test machine, and see how long upgrade takes.

daveronson · Post by **daveronson** » Thu Jun 29, 2006 8:24 am

I thought I'd follow up to let you know the upgrade went flawlessly. The upgrade took 2 hours start to finish for our 3GB Vault DB, including a manual backup of the database, a post Vault upgrade to SQL SP4 and the required "-SupportComputedColumn" switch added to the maintenance plan steps.

Thanks for making the upgrade so painless.

Dave