Large Vault database

sswanson · Post by **sswanson** » Thu Jun 28, 2007 9:50 am

We've been in the process of moving our SourceSafe repository over to Vault for a while now, and lately the imports have been slowing down considerably. I'm assuming this is because the current project we're bringing over is rather heavy on labels. What I hadn't expected though was the current size of the Vault SQL database which is approaching 50 gb where as our original SourceSafe database was somewhere inbetween 12-20 gb. Is there something going wrong or is this normal to have that sort of expansion?

lbauer · Post by **lbauer** » Thu Jun 28, 2007 1:50 pm

That doesn't seem out of line. It's also possible there's some unused space in the SQL database, and a shrink operation might bring it down some.

sswanson · Post by **sswanson** » Fri Jun 29, 2007 8:11 am

Ok, with the database at that size could it be affecting backup operations and obliterations? Both are currently failing.

lbauer · Post by **lbauer** » Fri Jun 29, 2007 3:07 pm

It could affect obliterate, as obliterate takes a great deal of time and this can lead to some sort of timeout, either on the network, SQL Server, etc.

Backup should work, though. Have you tried backing up with SQL Server backup, rather than through the Admin Tool? SQL Server should be able to handle large databases. If you don't have adequate hardware, you could be running low on memory, disk space, or CPU.