AnsweredAssumed Answered

Database portion of version upgrade

Question asked by rf-srns on Jun 13, 2011
Latest reply on Jun 13, 2011 by mrogers
We have not yet attempted an upgrade, but now need to go from 3.3.2 Enterprise to 3.4.2 E.  The documentation does not make it abundantly clear to me exactly how to handle the filesystem and database.  I understand that I am to do a "clean" install of the new version, and then basically point that installation at the backups made from the existing version.  The filesystem (root.dir) part seems straightforward:  just overwrite the directory.  I am less clear on the database part.  Do I create a new database when doing the clean install, and then just modify the file to point to the old database?  Or am I supposed to somehow restore the old SQL data from the backups to the new database?  Will either approach work?  I understand that I have to get all this kosher before restarting the new installation, but want to be certain I am taking the easiest route, as when I do this on our production instance, I cannot afford to lose the data.

We are running 3.3.2 Enterprise on Windows Server 2008 R2 64-bit, and SQL Server 2008.

Thanks for any insight you are willing to share.