Is my upgrade strategy sound?

[meschulte]

We are starting a new long term project and moving our old project to the back burner. We have version 3.5.1 of Vault and are using Visual Studio 2005 with about 10 people in the group. We are moving to VS 2010 and plan to start a brand new project using the latest version of Vault. Our old db is about 5G in size and we would like to start with a brand new db (but keep the old one available).

So, my plan is to buy the upgrades to our licenses and then upgrade Vault to version 5 (using the method mentioned on the knowledge base posts of going through multiple version upgrades) with our old db. After we are in version 5, I would like to create another instance of the SQL Server as in the following link:

http://msdn.microsoft.com/en-us/library ... L.80).aspx

Then I theortically could leave the old db in one instance of SQL Server and then create a brand new Vault db in another instance. So when we need to look at the old db, we can get to it (but we will mainly be working in the new db).

So my questions are... will this work? Will we be able to buy one set of licenses but access both dbs on one machine? Do we just put in "machineName/SQLInstanceName" as the Vault Server name when we log in?

[lbauer]

So my questions are... will this work?

Not the way you'd like. It's possible to have two SQL Server instances, so technically, you could have two different Vault databases on one machine. However, the Vault Server can only communicate with one sgvault database at a time. You'd need another web server to have easy access to two different Vault databases.

Another idea would be to upgrade your existing database, then add new repositories for your new code. If you wish, you can restrict access to the old repositories by using Folder Security or Repository Access settings. If a user has No Access, they wouldn't even see the repository in the repository list. This setting is in the Admin Web Client under Source Control Repositories->(Repository name)->Repository Access.

HTH