SQL Server access

MLato · Post by **MLato** » Mon May 21, 2007 9:33 am

We are about to install our recently purchased Vault system. However, our DBA is uncomfortable providing an administrator-level account for installation. Is it possible for the DBA to create a Vault database on our SQL Server 2000 system and provide an account with dbo access to it?

lbauer · Post by **lbauer** » Mon May 21, 2007 3:05 pm

The account used by Vault to access the database during regular operaitons does not need to be administrator level. However, during installation, the installer does need to use an account with SA priviledges (or equivalent) so that the installer can create the database and the login and Vault dbo.

Vault will use either the ASPNET account (NT Authority\Network Service or Machine\ASPNET) if you are using Windows Authentication, or will create an sgvaultuser account for SQL Server authentication.

You can also create a custom account for the IIS Process Model that Vault will use to access SQL Server if you are using Windows Authentication. For details see our install guide:

http://www.sourcegear.com/vault/support/install1.html

digitall · Post by **digitall** » Fri Jun 01, 2007 11:50 am

I am kind of in the same boat. I used to have Vault at my old employer and loved it. My new employer uses TFS (yes, it's as bad as everyone has probably heard) and I'm trying to convince them to switch to Vault. I need to install the database on a shared server though. Is there any way I can specify the database to use (it's an empty one, I just won't have sa access to it) instead of the installer trying to create one? A friend suggested I let the installer run and create the DB on a local box and then transfer the tables/sprocs to the shared server and change the Vault config. Is that an option if selecting a specific database isn't?

Post by **jclausius** » Fri Jun 01, 2007 2:06 pm

In regards to Vault 3.5.2, you could install on a virtual machine, detach the database, copy the database over to the new SQL Server, but the setup of the server is a real pain.

Contact support at sourcegear dot com, as they have instructions regarding an "x-copy" installation. However, please make sure you have a good deal of spare time as all of the permissions and configuration changes you need to manually make will take some time.

digitall · Post by **digitall** » Fri Jun 01, 2007 2:11 pm

Hmm...does version 4 support this (since it drops next week) type of scenario? Getting the schema isn't an issue...I'm just trying to host it on the shared server since I'm a bit lazy when it comes to backing up my personal server. What kind of SQL permissions does it need once the DB is created? Will it work in a shared environment where I can give it full dbo access on the specific database?

Post by **jclausius** » Fri Jun 01, 2007 3:13 pm

No. Vault 4.0 is going to make a larger number of database changes, so xcopy installation has yet to be worked out.

digitall · Post by **digitall** » Fri Jun 01, 2007 4:04 pm

OK, that works. I'll just install it locally for now and if something changes I'll go remote.

Guess I need to start backing this box up now...