3.0.2 Slow to Checkout...

[neal007]

Hello,

Thank you for the outstanding product! It's a life saver!!!

I am a one man show here and I have a dedicated Dell server in house running Windows 2003 Std, SQL Server 2000 and have Vault 3.0.2 installed. My checkouts, such as for a single file in VS.NET 2003 can take up to 30-60 seconds at times, and I've been using Vault, so I know it's not a IIS recycling issue. I do have folder security disabled in the Vault Admin.

Are there any articles here on optimizations, or any steps I can check to ensure I have everything configured correctly for optimal performance?

I also noticed, having used Vault for quite a while, a ton of folders on my C drive on this local machine that appears to be Vault created information yet Vault is on the server, not on this dev machine. How can I also prevent these folders from adding up over time, there were hundreds upon hundreds and eating up a tremendous bit of C drive space.

Thanks!

[jclausius]

neal007:

First, I would suggest making sure the disk drives where the database files are defragmented ( while SQL Server is not running ). In some rare instances, file fragmentation can bring SQL Server to its knees.

Next, I would suggest going over this article - Maintenance: Vault/Dragnet database(s). I also would stree the most important tables for checkout are tblcheckoutlists, tblcheckoutlistitems, and tbltreerevisionfolders.

Since list overhead can get big, we recommend only locking files you plan to modify. If you will not be changing the file, leave it unlocked. How many files would you guess are checked out at any given time?

As for the folders, were they named _sgvault? If so, have a look at the KB article - Understanding the Vault client. It explains the use / storage of these files.