Upgrading from SQL 2000 to SQL 2005

[tjruska]

I have seen a number of posts regarding this. And I just want to understand why does one need to uninstall Vault and reinstall it again pointing to the new instance? Isn't Vault just a web service(s) and the location of the database is defined in the web.config? Why can't one just update that to the new instance of the Vault database vs. uninstalling and reinstalling? That seems easier to me. Or am I totally missing something?

In my situation we want to upgrade the existing database from 2000 to 2005 and keep the existing Vault server intact which I have upgraded to v3.5.3. The database and Vault server are separate. If this combination is successful in DEV, we will be doing this in production soon.

Thanks, Tom

[Beth]

The reinstall would be for if you are moving the SQL server. If you are just doing an in-place upgrade of SQL, nothing needs to be done to Vault. Do make a backup first of your databases though before upgrading SQL.

If you are moving SQL to a different server, then you will want to refer to the following KB article that details out two ways to accomplish that:
Moving the Vault or Fortress Databases