DB times out on large folder branches

[mayfield]

RE: Vault 4.1.2

I have a large-ish folder (1.3 GB) and trying to branch it results in an SQL Timeout error after about 5 minutes. I've confirmed that my database server (MS SQL 2K5, quad core, 4 GB RAM) seems to be constrained by the fact that the only 1 CPU is being hit during the process and gets pegged at 100% utilization (yes, I've confirmed that SQL Server is configured to use all 4 CPUs).

Is there a way to increase the timeout value that Vault uses during branch (or any) database operations? I found nothing in the options dialogs, but I'm hoping that maybe there's a registry setting that it uses, or perhaps ADO.Net has a "master" timeout value (that I could perhaps increase) that Vault just defaults to.

Any insight would be appreciated.

Scott Mayfield
mayfield@magicworld.com

[lbauer]

You can change the SQL timeout value in the Vault.config file in Inetpub\wwwroot\VaultService.

Look for the line
<SQLCommandTimeout>360</SQLCommandTimeout>.
Change the number to something bigger, like 3600 or 7200

Let me know if this does not resolve the problem.

[mayfield]

I found that setting right after posting the message I did find that I had to restart the vault site before it would take effect (expected that) and upon retrying the branch operation, it hasn't crashed yet and based on the status messages, it appears to be further along in the process than it had gotten in the past. Thanks.

[lbauer]

Thanks for the update. Let us know if you need further help with this.