sgvault_log.LDF is enormous

[koconnor]

We run Sourcegear Vault version 3.0.7.2863 for our source control. Recently we noticed our transaction log sgvault_log.LDF is enormous. Roughly 79GB and growing.

What can we do to shrink the size of the transaction log? Can we truncate it in Enterprise manager and migrate to a new one?

[jclausius]

Did someone change the recovery model of the database?

In any case, after you have a valid database backup, look at running - BACKUP LOG sgvault TRUNCATE_ONLY, and then DBCC SHRINKDATABASE('sgvault', 0, TRUNCATEONLY) to remove the unused portion of the database's log.

[drmccue]

The SQL syntax for the first step is:

BACKUP LOG sgvault WITH TRUNCATE_ONLY

[jkp*74]

Which recovery model do you recomment? I have changed it to Simple, is that OK? Can i run the log truncate with active users logging in? (Sorry, i am totally new to SQL Server )

[jclausius]

If you do full database backups or a backup through the Vault Admin Tool, then simple recovery mode is recommended.

Note, Vault 3.5.2 and later versions changed some of the data storing methodologies, reducing database size requirements. So database storage issues have been minimized in later versions of the product.