Deadlocks when branching large projects

[Lysaer]

Hi, I've searched and not found anything, so maybe this is a new topic.

We are using Fortress 2.0.2 on a standalone Windows 2003 server, pointing to a separate MS-SQL 2008 database server.

Today, when a developer attempted to branch a project containing 4,300+ files, 400+ folders, taking up local disk space of around 40mb, the database experienced a large number of deadlocks. No other Fortress client was able to access during this time. After killing the client branching, everything cleared up. This was repeatable and only appeared to happen with that particular project.

The project has been branched successfully in Fortress 1.1.4 and previous versions.

The question now...is the branching the problem, or a symptom of a possibly corrupted repository table?

[lbauer]

This can be caused by something other than database corruption. The branch may have grown over time or accumulated more history, which can cause the branch to take longer.

We'd like to see a copy of the Fortress log so we can better answer your question. The Fortress server log is sgvault.log and is in %windir%\temp\sgvault on the server machine. Send the log zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[lbauer]

If you're running into database performance issues, it also helps to do regular database maintenance.

Details here:

http://support.sourcegear.com/viewtopic.php?t=2924