Migrating to SQL Server 2005..

[sachinkas]

We are migrating to SQL Server 2005 which is going to be on a new server. Vault is so critical to our development that I cannot afford to keep it offline for long and if it does not work, thats it. So I have a few questions to be safe:
1. How to determine the version no of server. I know the client is 3.1.0, not sure if server is the same.
2. What would be the best and safest way to do the migration. I have read this article:
http://support.sourcegear.com/viewtopic.php?t=924
But I do not have the version 4.x. So my question will be how do I upgrade to this version.

Again I want this to go very safe. I tried to play with the Web.config to point to the new server etc. but always it would give:
Login failed for user 'sgvaultuser'.
I wonder where that comes from because we do not have it mentioned in the web.config.
I know the Admin password (the one which we connect to the client)

For me the best bet is to find the quickest way to first make it working on our new SQL server 2005 server and then try to upgrade. But how do I do make it work for SQL Server 2005 for version - 3.1.x

I am a bit skeptical about re-install because I do not want to end up not able to do anything after the re-install. But wont mind doing that too if that is the easiest way out

Greatly appreciate your help.

[lbauer]

But I do not have the version 4.x. So my question will be how do I upgrade to this version

Just to be clear--you want to upgrade to SQL 2005, however you do not plan to upgrade your Vault version. Is that correct?

[sachinkas]

Yes. My first task would be to upgrade to 2005. I am not yet worried about upgrading the Vault version

[lbauer]

These instructions are valid for Vault 3.1.
http://support.sourcegear.com/viewtopic.php?t=924

The difference is that 4.1 has two databases, and you only need to be concerned about the sgvault database in 3.1.

If you want to test this out first, you could backup a copy of the Vault database and restore it to the SQL Server 2005 machine. Then install Vault on a test server and point it to the database location. If that all looks fine, uninstall Vault on the test machine, leaving the database when prompted.

Then on the production machine, uninstall Vault, then reinstall, pointing to the new database location. The installer takes care of configuring SQL Server to communicate with your Vault Server by adding the database user, etc. I recommend this becasue your efforts to edit the web.config file were not successful.

[sachinkas]

Thanx. Worked perfect!!

[lbauer]

Glad that worked for you.