SourceGear Support

Unless you are short on space you probably shouldn't worry about shrinking your database or log files.

We are using 5.0.1 to 5.0.4.

You could also set the permissions at a higher level so that the file you are sharing is using inherited permissions only. When you share it to a new location it inherits the permissions there instead.

I have found the cause and I think it is a bug. If a developer has permissions anywhere in the repository to a file then they can affect that file in a folder they do not have permission to change. In our example, a developer has accidently branched from a share (instead of sharing) a file in a fold...

A developer recently broke a share in a folder that he had read only permision in. By broke, I mean that he turned the share into a branch even though he only had read permisions in the folder. Surely this cannot be correct behaviour. Please advise if it can be undone or am I up for a delete and res...

When I open a solution from VS2008 using the open from vault and I have not retrieved the solution and all of its projects before. I only every get the solution. The project files are never gotten and I have to use the Vault Clienbt to get the files anyway. This reduces the utility of 'Open from Vau...

Sometimes when performing tricky merges it is a comfort to check the changes in a file - but, although the UI offers a Show Differences option (right click on file in list of checkin details - accessed from list of versions in the merge wizard), it doesn't actually do anything until you exit the Mer...

How can I stop developers from branching shared objects. I have given them only read access to the folder but they are still able to branch a shared object. Is this as planned? I would have thought readonly would be, well, readonly. Branching sounds a little changy to me. I need the developers to ac...

Is it possible to order maintenance for an existing install or are you out of luck if you let maintenance (or Gold Support) lapse. We plan to upgrade from 3.1 to 4.0 and would like to put 4.0 on maintenance. When I tried that on the sourcegear store the cost of maintenance was zero. I would like to ...

We use Vault 3.1.2 and recently had an ISP outage that left us without internet access. No problems except that when the Vault client is started it does that version check. Which to be honest I am all for as I don't browse the support site daily to get the news about new releases. My problem is this...

That's really the problem I guess. The developer restriction would be the closest ancestor but if the architect is not a developer then full access is granted because of the greater permissions granted at the root of the project for Architects. I would have expected the Developer restriction to be i...

I have a problem withe the way the group permissions seem to work. To simplify my problem lets assume I have two main groups. Architects and Developers. Architects have full access to project A and partial access to Project B while developers have partial access to Project A and unique partial acces...

The files I am trying to obliterate have only one line of history - It is the creation of this file in the Snapshot. The files are massively shared around which seems to be the only 'special' thing about them. Yet still they will not obliterate. Any ideas? *EDIT* IF I branch the individual files tha...

Wow, The 3.1.1 update has certainly improved Obliteration. Although now it appears I cannot obliterate a shared file. I try and I get the standard Unable to Obliterate - All branches of an item must be obliterated message - but there are no branches listed. Any ideas? *EDIT* It seems that some share...

I am having some difficulty running obliterate. I realise that it requires some time to check all those branches and whatnot - but it takes too long and things timeout or fail. I was wondering if it would be possible to wrap all that obliterate control stuff into an application that directly interac...