SourceGear option to only keep latest version of file?

[thale013]

I recently imported into SourceGear from Visual SourceSafe6 and wanted to know if SourceGear had an option to only keep a copy of the latest version of a file. The reason I ask is that we keep a lot of library files, help documents, DLL's, etc. in our SourceSafe database and if we maintained revision history for those files going forward with SourceGear, the size of the database would grow very quickly.

Thanks,
Tyler

[Beth]

Vault does not have the option to only keep the latest version.

If the DLLs are something you build, then the files that build the DLL should go into Vault instead of the DLL file.

If the DLLs files are not something you build, then how are they changing often?

[thale013]

We have DLL's that we build and DLL's that are provided to us by 3rd parties. For the DLL's that we build, your suggestion is correct, we could (and do) maintain the source code to build those DLL's in our repository. My main point is that we have other, different kinds of large files besides DLL's that we are changing often and storing every revision of them in the SourceGear is going to cause the database to get large, very quickly.

[Beth]

What are the other types of large files?

[thale013]

Documentation files and static libraries...it looks like we will try to find a different way around this issue since it isn't supported.

[Beth]

Here's an idea that might work for you. If you're not using Visual Studio bindings, you could place those kinds of items into their own repository. You would then maybe track for a certain number of versions, then delete the repository they are in, create a new repository and add them in again. Deleting repositories completely deletes the information from the database and doesn't affect other repositories. That way you'd just keep a few versions of that file in at a time, and then start over again with the latest.

[smiller]

We have a similar one-version requirement. We keep our test baselines in our VSS repository. Each of these tests baseline datasets may be up to 500MB. We want to maintain a version/change history, but only want to store the latest version. Beth's idea to wipe/recreate the repository periodically would result in us losing the change history along with the multiple versions. Ideally, we want the master copy of everything needed to feed our nightly build and regression test process to come from the repository -- to the extent that we even store the scheduled task .job files and the linux cron tables in the repository.

What prevents Vault from having this capability? The marketing spin is that we can have all of the VSS features in a modern, scalable, supported system. Sounds good; but the devil is in details like these.

[Beth]

smiller: I'm a little confused by your requirements. You say you have a one-version requirement, yet you want the history. The history is how you get your multiple versions. Vault doesn't store an entire new copy of the file each time a change happens. Just a delta of the changes. Can you explain what you mean by the history you want yet only having the latest version of the file?