- Beside sgvault and sgmaster db, can I create another database that Vault server can also support? In other words, can Vault server support more than 2 databases (other than sgvault and sgmaster db)? The reason for multiple db is because our database is getting big very fast and we want to split it out to multiple ones for security and performance purposes. That leads to the next question
- What is the biggest db file that we should keep? Any recommendation if the db size getting too big?
- What is the max file size that we should set for "IIS File Upload Limit:"? What if we set beyond the recommendation? Any thing we should concern about if we do that?
- Does the user's system requirement needs to adjust as the Vault db getting bigger?
v4.1.4: Database size and number of db support
Moderator: SourceGear
v4.1.4: Database size and number of db support
I have serveral questions:
Re: v4.1.4: Database size and number of db support
Vault doesn't have the ability to connect to other databases.
The database size is dependent upon the version of SQL Server that you have. As long as you don't hit those limits, then Vault can work. What makes a bigger difference is your hardware.
I don't know what's the biggest a customer has ever tried, but I've seen ones as large as 250 GB.
The max file size allowed is also determined by SQL. I think SQL Server won't allow more than 2 GB in one cell, so that would be the initial file size limit. Setting beyond that shouldn't hurt anything, but it won't gain you anything either.
To handle a large database, you just need the hardware that can do it. Also, using our performance recommendations and SQL maintenance recommendations, you can keep it optimized. The articles you want are Recommendations for Optimal Vault Performance and Maintenance: The Vault Server database.
Sometimes how Vault is used is what is making the database grow fast. If you would like, we can discuss offline how you use Vault and if there would be a way to make that more efficient. Of course, we have some customers who just really have a lot of code, and there's nothing wrong with that. Just planning accordingly can make a difference with large teams and large amounts of code as well.
The database size is dependent upon the version of SQL Server that you have. As long as you don't hit those limits, then Vault can work. What makes a bigger difference is your hardware.
I don't know what's the biggest a customer has ever tried, but I've seen ones as large as 250 GB.
The max file size allowed is also determined by SQL. I think SQL Server won't allow more than 2 GB in one cell, so that would be the initial file size limit. Setting beyond that shouldn't hurt anything, but it won't gain you anything either.
To handle a large database, you just need the hardware that can do it. Also, using our performance recommendations and SQL maintenance recommendations, you can keep it optimized. The articles you want are Recommendations for Optimal Vault Performance and Maintenance: The Vault Server database.
Sometimes how Vault is used is what is making the database grow fast. If you would like, we can discuss offline how you use Vault and if there would be a way to make that more efficient. Of course, we have some customers who just really have a lot of code, and there's nothing wrong with that. Just planning accordingly can make a difference with large teams and large amounts of code as well.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support