We have a multimedia team that would like to store their files (flash, audio, documents, video, etc.) files in Vault to keep track of their versions. Most of the content they would desire to store in there would be binary files. While they could begin to try to differentiate between "source" and "destination" type files, it would be useful to them to not have to try to train their folks in making all these distinctions.
At first, I was going to have them comingle their stuff with our Development project, but now I'm thinking that's not the greatest idea.
1. Do you agree that we shouldn't just toss everything into one repository? Or does it really matter?
2. Aside from the management issues, I presume there are performance implications to storing boatloads of files inside Vault.
3. Are there any suggestions for doing this in a better way (organzing the structure, etc.)?
Just estimating, they currently have about 20 GB of files. Not all would go in, but it's a good number to work with. We are currently using Vault 3.1.9.
Questions about adding 20 GB of media into Vault
Moderator: SourceGear
20 GB of files isn't a problem. It will depend a bit on the size of individual files, but the database over all should be fine in size.
1) Multiple repositories is a good thing and can help improve performance immensely. If you need to share files between projects though, then in one repository is better.
2) There is a chance of a performance hit, but this is stuff that can be managed with proper hardware and configuration.
3) The key is where the "break points" are. By that, I mean at what point does a project or chunk of data separate off from other stuff in the repository? One doesn't want to necessarily get repository happy and make a 100 repositories either. I've attached a document with a little picture to help explain.
You will find that you will get better performance by getting to either Vault 3.5.3 or the latest version of 4.0.6.
1) Multiple repositories is a good thing and can help improve performance immensely. If you need to share files between projects though, then in one repository is better.
2) There is a chance of a performance hit, but this is stuff that can be managed with proper hardware and configuration.
3) The key is where the "break points" are. By that, I mean at what point does a project or chunk of data separate off from other stuff in the repository? One doesn't want to necessarily get repository happy and make a 100 repositories either. I've attached a document with a little picture to help explain.
You will find that you will get better performance by getting to either Vault 3.5.3 or the latest version of 4.0.6.
- Attachments
-
- Repository layout.doc
- (26 KiB) Downloaded 212 times