295MB in VSS, more than 4GB in Vault?

sziszko · Post by **sziszko** » Wed Mar 01, 2006 2:56 am

Hi, we are just evaulating Vault and do a VSS import as a first step. The size of the VSS database is 295MB. Less than half of the progress bar is filled, but the size of the sgvault.mdf is already 3.76GB. We have SQL Server 2005 Express only for this test, it has a 4GB limit for database files. Is it possible that a 295MB VSS database grows over this limit?
The VSS Check&Fix found no errors. There are many files and many labels.

lbauer · Post by **lbauer** » Wed Mar 01, 2006 9:27 am

When Vault imports labels, it essentially re-creates the project at the time of the label. Later, files that were deleted after the label are deleted in Vault (but not obliterated), etc. With regular SQL Server, database maintenance can be run later to shrink the database to a more manageable size.

I'd suggest uninstalling and not keeping the database. Then reinstall and do the import again, this time importing only your most needed labels.

sziszko · Post by **sziszko** » Thu Mar 02, 2006 6:10 am

I have tried it now with a smaller branch, it has only 23 labels, the VSS size is 202MB. VSS Check&Fix was OK. The import finished, I had one error reported (see below), DBCC CHECKDB was OK.

An error occurred while trying to end a transaction.
An exception was encountered during the transaction. Exception: VaultServiceAPILib.VaultSoapException: 1011 : FailInvalidSessionToken
at VaultService.VaultServiceSystem.ValidateToken(VaultAuth va)
at VaultService.VaultService.EndTx(String strTxID, Int32 nTxAction, DateTime& dtTxBegin, Int64& nNewRevision, VaultResponseItem[]& responses) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.ClientService.VaultService.EndTx(String strTxID, Int32 nTxAction, DateTime& dtTxBegin, Int64& nNewRevision, VaultResponseItem[]& responses)
at VaultClientNetLib.VaultConnection.EndTx(String strTxID, Int64& nNewRevision, VaultResponseItem[]& responses, Int32 nAction, DateTime& txBeginDate)
at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)
Transaction failed
10:02:03.2001339

The result of label import was quite disappointing. After asking for a history of a file, not only the order was messed up, but the linking of dates, user names and labels were in general wrong. Although all labels were present somewhere.

Then I checked the size of the db which was over 3GB, so I obligerated the temporary projects which were deleted (you mentioned them above), and shrinked the db. Now it is 2.84GB, which is still more than tenfold increase.

But it would not bother me, if the label import would work, but it does not. Is there any chance for a really working version soon? If not, we can forget Vault

lbauer · Post by **lbauer** » Thu Mar 02, 2006 2:35 pm

The display of labels in history is something we're still working on for Vault in general, not just imported labels. There have been different opinions on how to handle this. Right now, labels appear in Folder History next the folder version that existed at the time the label was created.

So if you label $/Foo and Foo was last modified Tuesday at 3 p.m., the label time in Folder History would be Tuesday at 3 p.m. Because of the way labels and versions are re-created during the import, imported labels do look out of order. However, labels in Show Labels should show the actual dates of the label operation and the list of labels should be in date order, and easier to find, in Vault 3.1.7.

If Show labels still doesn't look right, send me a screenshot and we'll investigate further. Email linda at sourcegear.com.