It seems that our DB is growing too big. It appears to be growing 1GB every three days or so.
How I know this is because I see the nightly back-up file size.
Has anyone experienced this behavior?
Is there a way to verify that the growth is actually because our runs and not something else?
Any help/information will be greatly appreciated.
I see that Sam's issue was handled via a Support case. For future visitors, note that database size has a lot of variables. Some of the more important ones include the number of snapshots created each day, and the frequency of changes to source code files (since snapshots include the source code as of the time of the analysis build). Note also that the backend database does not automatically reclaim freed space--it simply marks it as freed, to be cleaned up later (this is a performance feature of most SQL databases). Fortunately, that freed space is not present in the backups.
Thus, to reduce the amount of freed space that accumulates in the database we recommend restoring from a database backup periodically. That will help keep the amount of unoccupied space in the database to a minimum.
There are other strategies for reducing database size over time, such as removing old snapshots. These strategies come with their own set of pros and cons, so please work with Coverity Support as you develop a space management strategy.