Do any of you has concerns about the growing size of your sgvault DB? Big size takes more time and space for back ups.
I wish to use Vault server for codes and small documentations that support the codes. As users get used to Vault, some find convenient to use Vault as a LAN storage device. They check in big binary files like DB backups, video or big PDF. In addition, most of the users are not aware that a deleted file still consumes storage space in Vault server.
I would appreciate any advice on the good practice to manage these big binaries.
Thanks very much in advance.
How big is your sgvault Database?
Moderator: SourceGear
It's difficult to have an official answer when much depends on user preferences.
A large database is not necessary a problem. Technically, Vault database size is limited only by SQL Server limits. We have customers with databases of 160 GB and more. However, as Tri said, you need adequate hardware and disk space when your database grows. You should be doing regular database maintenance.
But Vault performance depends more on how many users/transactions/checkouts there are, rather than database size.
Some users use Vault only for source files, and archive large binaries elsewhere; other users like to have everything in one database.
Use Vault in the way that best meets your needs.
A large database is not necessary a problem. Technically, Vault database size is limited only by SQL Server limits. We have customers with databases of 160 GB and more. However, as Tri said, you need adequate hardware and disk space when your database grows. You should be doing regular database maintenance.
But Vault performance depends more on how many users/transactions/checkouts there are, rather than database size.
Some users use Vault only for source files, and archive large binaries elsewhere; other users like to have everything in one database.
Use Vault in the way that best meets your needs.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager