After importing a VSS database (that showed 0 errors via Analyze) [using 3.0.5] I got a couple of errors, the last about Label Verification. I assume because of this I now have close to 3000 VaultImport lines in my history, which means I can't get a complete project history, because it exceeds the 10,000 line limit (why is there a limit?). Two questions: 1) Is this an indicator that my import failed and I should not put the Vault system into production? I know I'm missing that one label across a number of sub-projects, but I can live with that (though obviously I'd rather have the label) 2) If no, is there a way to get rid of all those VaultImport lines.
Thanks,
Eric T.
3000 VaultImport entries
Moderator: SourceGear
attached files...
Sure, attached are an image of a history, plus the errors generated by the import
- Attachments
-
- Screen shot showing a subset of the VaultImport lines
- vault1.gif (63.33 KiB) Viewed 8203 times
-
- error messages.txt
- Extract from the screen display at end of import. I also have the entire import log if needed
- (539 Bytes) Downloaded 934 times
These files are added and deleted so that they can be included in labels. In VSS, the items were moved or deleted after the label was applied to them. If you do permanently remove them from your Vault database, that would corrupt all of the labels that depend on them. The short answer is, they were put in Vault so that they could be included in imported labels, and you should just leave them alone. They are not a sign of an error in the import.
One other note, the history for any item is there, but being limited.
You need to do one of two things if you want an view more history:
1) Filter the history a bit to fit within your defined history query size ( < date; > date; by a user; only certain items, etc ).
OR
2) Increase the size of the return set in the History Options so > 10,000 rows are returned within the query.
HTH
You need to do one of two things if you want an view more history:
1) Filter the history a bit to fit within your defined history query size ( < date; > date; by a user; only certain items, etc ).
OR
2) Increase the size of the return set in the History Options so > 10,000 rows are returned within the query.
HTH
Jeff Clausius
SourceGear
SourceGear
Leaving them in is quite ugly. This does not make it a drop-in replacement for VSS. Couldn't they be removed from the view because they mean nothing to users, and are only there for internal reasons?
Also, 10,000 rows is a hard limit imposed by the Vault system.
What I'd really like is to search for all rows since a previous label, but I can't do that, since labels can't be entered as a search criterion. For instance I want to get a quick view of all the files checked in since the last label. How can I do that? So I do a search since the 1st of March because it was sometimes around there, but I get 3065 rows back, of which ~2700 are the silly Vault Label Import rows.
Also, 10,000 rows is a hard limit imposed by the Vault system.
What I'd really like is to search for all rows since a previous label, but I can't do that, since labels can't be entered as a search criterion. For instance I want to get a quick view of all the files checked in since the last label. How can I do that? So I do a search since the 1st of March because it was sometimes around there, but I get 3065 rows back, of which ~2700 are the silly Vault Label Import rows.
I've created a Request for Feature Enhancement (RFE) to raise the 10K limit. It should probably be higher for cases like these.
I also added your name to the RFE to query history with the use of a label name.
If you scroll through the list, was the "admin" account responsible for every change to the IPCap folder?
I also added your name to the RFE to query history with the use of a label name.
If you scroll through the list, was the "admin" account responsible for every change to the IPCap folder?
Jeff Clausius
SourceGear
SourceGear
10,000 row history
Sorry, missed the notification. Thanks for making this an RFE. As to admin, no all admin did is the import. Now, in hindsight, something had gone wrong with the import, and all those lines might be a remnant of the bad stuff. I'm missing a few labels that I know used to be in VSS, and I think there's even some code that didn't come across, but since it was in a basically dead branch, I didn't notice it until recently, and I'm assuming it's missing since the import.