SourceGear Support

If you create a new label, can you delete it? No, I can't. New labels are created just fine, but deleting it causes the same error. Do you get this error just on labels prior to the upgrade? No, also on new labels. Does deleting a label fail on any older label? Yes. What version of SQL Server are y...

jtaylor wrote:Unfortunately, we from time to time have users who want to use the labelling feature for their own purposes and apply "misguided" labels.

Beth, add my vote for this feature.

Jason, just curious though, it's not exactly technically harmful is it to have occasional misguided labels?

On a test server I have upgraded our 3.1.7 to 3.5.1. Everything seemed fine until I had to delete labels (log attached). On another clean 3.5.1 install deleting label works fine, so I assume this is something to do with an upgraded database. Any resolution? # SourceGear Vault Server ----9/22/2006 12...

I'm currently going to the process of upgrading our custom Vault tools to 3.5.1 in preparation for the upgrade. I'll document issues I am facing, maybe it will be of use to others. The basics: Replace API dlls Get plugin lib from Vault server bin dir Issues so far: Date time in history requests, lab...

We have quite a few bits and bobs of custom code on Vault API built up over the year. I am going to use the opportunity of upgrading to Vault 3.5 to rationalize and refactor some of these tools. Is it OK if I upgrade these tools to .NET 2.0/3.0, referencing 3.5.1 client api assemblies? One of the to...

An addition to this that I didn't think of. You can install another instance of SQL server and then perform your second install to that I think. Unfortunately, as I mentioned above, I don't even have that luxury. There are several reasons for this dry run, not just fear of corruption etc, but we ha...

Is it possible to install Vault 3.5.1 upgrading a 3.1.7 db with a name other than sgvault? The reason if for upgrading dry run we are restoring the backup of the production db to sgvault2 on the same db server (no, we haven't got another db server instance that we can use for this!)

I don't believe deleting labels will help much. Since we've pretty much done all the suggested steps as a matter of process (weekly DB tuning etc), I went and deleted the unnecessary labels anyway. About a thousand build labels were deleted, and now the merge process works as normal. As a result we...

Somewhat related, on Vault 3.1.7, merging fails when the wizard was "retrieving origin history" due to (from server log): BeginLabelQuery returned: FailDBInsert I think the beginlabelquery timed out. We do have quite a few labels due to our build process. Would it help if we delete old lab...

jclausius wrote: If you have any problems compiling against the new libraries, just post back, and I'll explain the changes.

Does that mean that as long I can compile correctly I can assume everything is OK?

Because release notes says Vault 3.1 client is not compatible, does this means we need to change our client APIs assemblies as well?

And is there any known breakage in API, or can we just drop and recompile.

Good. As a background this problem stems from the fact the we never use item comments, and in the few times it's set is because programmer error when using Visual Studio integration (it displays a 'checkout comment' box, invariable some junk gets typed in there). The 'proper' comment then is typed u...

Another way I may have found is through TxDetails: myClient.Connection.GetTxDetail(myClient.ActiveRepositoryID, vhi.TxID, ref changesetComment, ref vtdhitems); So after I found the history items, instead of getting comments from VaultHistoryItem, I use the TxID to get TxDetails instead. It seems to...

Another way I may have found is through TxDetails: myClient.Connection.GetTxDetail(myClient.ActiveRepositoryID, vhi.TxID, ref changesetComment, ref vtdhitems); So after I found the history items, instead of getting comments from VaultHistoryItem, I use the TxID to get TxDetails instead. It seems to ...

Here's some information about where comments are found in history: http://support.sourcegear.com/viewtopic.php?t=4303 In the command line, the History command returns only one comment -- the item comment or, if there is no item comment, it returns the changeset comment, but not both. This would be ...