Moving db to new server

[brian60640]

Our original repo machine is on its last legs.

We want to put the db on a SBS server with MSSQL in an instance MyServer\Repository. We are going to leave the vault front end on our crappy server because, in theory, getting the front end installed is trivial. Plus there are rumored Sharepoint/Vault problems and nobody wants to mess with Sharepoint.

We backed up the db and did a restore with move. The db looks fine to us. We can't seem to get vault to access the db, even after hacking web.config.

1) Can you have VaultService.asmx on one server and the data on another?
2) What is the secret?

-Brian

[lbauer]

1) Can you have VaultService.asmx on one server and the data on another?

Yes.

2) What is the secret?

It would probably be easier to uninstall Vault then reinstall, pointing to the new database instance. Since the database is now on a different machine, use a custom account for the IIS process model, or choose SQL Server authentication in the SQL Server setup portion of the installation.

The default install for Vault is to use the machine account (Network Service or Machine\ASPNET), but these are local accounts and don't work to connect across the network.

Also, when connecting to SQL Server during the installation, specify the instance -- MyServer\Repository -- instead of the default, (Local).

See our installation guide for more information about these options.
http://www.sourcegear.com/vault/support ... orial.html

[brian60640]

The db is named sgvault but the installer (3.1.9) doesn't detect it. It wants to create an all-new database.

Can we fix this, or should I just let it create a new db and restore over it later?

[lbauer]

During the installation are you pointing to the instance on the SQL Server machine? -- machine_name\instance_name -- in the Connect to SQL Server screen of the installer?