SourceGear Support

Ah, I've just spotted the v4 info tucked away here: http://www.ericsink.com/entries/SourceG ... tress.html
I'll need to curb my enthusiasm for a while longer.

Here's where I'm up to now. I'm convinced that the export is a totally separate problem. Whatever bad data is causing it, it's not affecting our day-to-day work, so I'm going to ignore it for the moment. I have been able to obliterate everything I've wanted to on the copy of my database, so this iss...

Performance: We usually have 8 to 10 users connected throughout the day. The main source folder has 11,000 files in 400 sub-folders. It can take up to an hour to do a fresh Get on this folder. This time has slowly been creeping up as our database size has increased. Export: I've increased the timeou...

I've not seen the old obliterate, but the proposed option does sound very useful.

(If people are hunting around for obliteratable branches, is there any way to generate a list of these using the Vault Command Line Client?)

I forgot this question:

- is there a better way of analysing branch sizes than by exporting them? (I only need an approximate idea of relative sizes)

I am trying to export branches, primarily to give me some idea of how much of my database each one is using. However, although I can export simple branches, the first two big branches that I've tried have failed. We are using Vault 3.5 with 10 users; we have a 6GB database with 10 repositories (the ...