SourceGear Support

Hi, Is there a way to configure the diff merge tool so that when you perform a folder diff you can view the individual files even if they do not have a peer? I'm not sure if this is possible in most diff tools but it would be really usefull when performing our code reviews (rather than having to ope...

Thanks very much. The email server we were using did not have relaying allowed. Now works fine.

Thanks.

I get this error when trying to use Vault email notification: ----2/22/2006 11:39:02 AM --()-- Error sending mail to Name@place.com at SMTP server mail-svr ----2/22/2006 11:39:02 AM --()-- Could not access 'CDO.Message' object. ----2/22/2006 11:39:02 AM --()-- Exception has been thrown by the target...

Hi, I've just upgraded to v3.0.7 and for most of my branches the old sourcesafe labels that were 'missing' are now listed in the vault history. They are however still missing from the history of our latest development path which is a 'branch of a branch'. Not sure why it is, I assume the fix made di...

Do you have an expected 2.1 release date?

We are about to cut our next release so I was wondering if this problem has been fixed yet? (since 2.0.2)

Thanks,
Paul

Just to say that after repeated backups of the log and the database the transaction log has now reduced to 1GB - which is a bit more manageable.

Thanks for the help.

We are using Vault 2.0.2. There hasn't been that many checkouts etc. We have had to do about 5 VSS imports though, some of which had to be deleted and re-done due to some early problems. Just to add some more info the the actual sgvault database is about 5GB now. I tried to do the backup of the tran...

We are using Vault 2.0.2. There hasn't been that many checkouts etc. We have had to do about 5 VSS imports though, some of which had to be deleted and re-done due to some early problems. Just to add some more info the the actual sgvault database is about 5GB now. I tried to do the backup of the tran...

After importing VSS databases into our Vault server I discovered that the sgvault_log.ldf file in SQL2000 has grown to over 11GB.This has caused big issues with our server running out of space, which in turn caused an import to fail. After freeing up some space I noticed that the log file grew anoth...

Ah, sorry - I obviously did not understand how the fix would work i.e. that it would indeed be retro-active. That is good news.

Thanks again.

I meant that once we do one branch, say to create a 6.6 release, this path will not contain the old labels. Subsequently any further releases taken from this path will also not contain the old labels - as even if you have fixed the problem there will be no labels to copy. Anyhow, I think we have a s...

Just to give you an overview of our setup we currently support 3 versions of our product and hence require 4 source paths - 3 for maintenance purposes and 1 current development. When we are about to do a release we label the current development path i.e '6.5 code cut off' and then copy/branch the tr...

Do you have any idea of when this might be? It is a bit of a major problem as we've just moved our VSS databases over to Vault but have now stopped checking in changes for our next release because of this issue.

Thanks.

When I do a branch in Vault (v2.0.2) I noticed that although the entire history of a file gets copied, any labels do not. Is this to be expected? If so is there another way that I can create a copy of my source with its entire history?