v4.1.4: join database with different version

[kha]

I have upgraded my biggest vault database from 3.0 to v4.1.4. However, we have another db that is still using Vault 3.0. We want to put this v3.0 DB (2000) to the same SQL server (2005) with v4.1.4 DB and also upgrade it to v4.1.4 compatible so that developers don't have to have use 2 different Vault client versions and switch back and forth to work with these 2 DBs.

The problem I am foreseeing while thinking about how to do this:

1. In the same sql server, DB with same names are not allowed. I am not sure if the db has to be named "sgvault" or not. But the sgmaster db is automatically created when we upgraded. That "sgmaster" db name will be for sure duplicated with what is already there for biggest vault db (v4.1.4).

2. We don't want to lose the history of the Vault v3.0 db. So, thinking about joining this db with the exisitng v4.1.4 db, I am not sure if joining db will lose the history on v3.0 (or distort information on v4.1.4 vault db).

Any idea how I should approach this?

[Beth]

What I would suggest is upgrade your current 3.x database to Vault 4.1.4. Then in your database that was already at 4.1.4, make a new repository for the new data. You don't have to put it in it's own repository, but if they don't need to share code, then you will find performance is a little better. Also, you don't have to worry about file or label names at all that way.

Next, use our Export/Import tool that installs with the Vault client to export from the database you just upgraded to the new repository you have in the other database.

For performing these actions, you don't need to do anything with licenses. Just perform the upgrade and the Export/Import with the admin account. Don't let users check in changes to the 3.x database during this process.

[kha]

that works! Thanks, Beth!

[Beth]

Thanks for the update. Happy to hear it went well.