SourceGear Support

It seems like the first login after re-starting Vault Server is taking 6 minutes or more. This is per Client. If multiple people attempt the initial; login at the same time, it takes even longer. Also, its generally slow. Check Ins have increased from a few seconds to 30 seconds or so. This seems to...

I can't see the attachment so I'm adding that again - zipped it up this time

We are experiencing frequent spikes in sql server 2005 CPU activity of 50% in total and mostly (approx 100%) on just one of the two CPUs for around 8 minutes. During this time only one process is active on SQL Server and its running: sgvault.dbo.spgetrepositorydelta;1 (I checked a couple of times fr...

Its a while since we last spoke on this issue. :-) Go to VS Tools -> Options -> Environment -> Documents -> Verify "Allow editing of read-only files; warn when attempt to save" is checked. We already use this. VS will not allow the file to be saved. Its an error not a warning - when Vault ...

Rob, One of the biggest problem with Vault's presentation in this regard is deciding what was last merged for subsequent merges. We'll look to see if we can improve this when it comes implementing improvements in Merge Branches for Vault 6. Thats exactly it. First merge is fine. Each succesive merg...

Rob, Three way merging is available during normal operations. This happens when a file gets into a "needs merge" state. Most merge tools, including SourceGear DiffMerge from within Vault, already handle this. You invoke "Show Merge" and you can look at repository, common ancesto...

Rob, Sorry. I'm talking about changes to the Merge Branches tool, and the history which will be merged into the destination folder. Your post states, "Source code line changes being shown in the merge view when you are reviewing the changes file by file," While the Merge Branches does not...

I haven't attempted these kinds of merges for a while as they are a pain in Vault currently, so I can't remember the precise issues with the UI, but it was something like all changes that have already been merged into Trunk being shown again and thus needing to check through those as well, and not ...

Indeed, it does take a long time to merge a parallel version back to the Trunk. This post discusses some possible solutions: http://support.sourcegear.com/viewtopic.php?f=5&t=10514&p=43030#p43030. Its especially relevant when your merge to the Trunk takes place periodically. What Vault is mi...

Well I hope that if its limited by date, that it remembers the last choice used and makes it easy and quick to list recent changes.

Jeff, its the minor changes that you think are major and the major faults with existing features that you treat as minor. If you haven't listed changes to Merge and Shelvesets as major changes in 6, then you are not doing them or are only making minor cosmetic changes, much like the 'major' features...

I was very disappointed to see that neither Merging or Shelvesets are getting a makeover in version 6. The 3 new features described: content searching - that's what an editor is for; Event Notification - by email works very well for us, no requirement at all to integrate into the Client; Classic Cli...

I have posted complaints about ShelveSets before and would like my vote added to all the features that Virgil has requested. ShleveSets could be really useful as opposed to barely usable!

Its a failed GET.

This works intermittently. Most of the time it works, and has worked without fail for 2 years every night. Recently it has become more unreliable. So, I'm interested in what the causes might be so I can fix it.