Subversion versus Vault

WebDude picture WebDude · Oct 8, 2008 · Viewed 7k times · Source

Possible Duplicate:
Any tool to migrate repo from Vault to Subversion?

I'm currently reviewing the benefits of moving from SVN to a SourceGear Vault. Has anyone got advice or a link to a detailed comparison between the two? Bear in mind I would have to move my current Source Control system across which works strongly in SVN's favor

Here is some info I have found out thus far from my own investigations.

I have been taking some time tests between the two and vault seems to perform most operations much faster. Time tests used the same server as the repository, the same workstation client, and the same project.

Time Comparisons

  • SVN
Add/Commit    12:30 Get Latest Revision    5:35 Tagging/Labelling    0:01 Branching    N/A - I don't think true branching exists in SVN
  • Vault
Add/Commit    4:45 Get Latest Revision    0:51 Tagging/Labelling    0:30 Branching    3:23

(can't get this to format correctly)

I also found an online source comparing some other points. This is the kind of information i'm looking for.

Usage Comparisons

  • Subversion is edit/merge/commit only. Vault allows you to do either edit/merge/commit or checkout/edit/checkin.

  • Vault looks and acts just like VSS, which makes the learning curve effectively zero for VSS users.

  • Vault has a VS plugin, but it only works if you're going to run in checkout-mode.

  • Subversion has clients for pretty much every OS you can imagine; Vault has a GUI client for Windows and a command line client for Mono.

  • Both will support remote work, since both use HTTP as their transport (Subversion uses extended DAV, Vault uses SOAP).

  • Subversion installation, especially w/ Apache, is more complex.

  • Subversion has a lot of third party support. Vault has just a few things.

My question

Has anyone got advice or a link to a detailed comparison between the two?

Answer

Matt Lacey picture Matt Lacey · Oct 8, 2008

Having used both 'in anger' I'd choose Subversion (with TortoiseSVN) over Vault every day.

When I went from Subversion to Vault this is what I noticed:

  • Can't do a get latest of everything I haven't changed, out of the box, in one easy step
  • Can't easily see anything that has changed
  • Vault tries, by default, to make everything I haven't checked out read only
  • I have to check things out
  • It's really slow to load (vault client) as opposed to always being there in explorer
  • Client navigation more awkward - than using Explorer
  • Easier to compare to older versions
  • Spell checker when entering comments when checking in
  • Everything was quicker and easier!

Obviously some of this is down to the way that Vault was configured, but you get the idea.

I ended up writing a bunch of scripts to automate the things that Vault couldn't do, but even then there are limitation on what the commandline version can do. Plus the Vault API isn't documented.

Update
Please note the date this was oiginally posted. Both poducts have changed and been enhanced geatly since I oiginally wrote this.