sgvault_log.LDF is enormous

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
koconnor
Posts: 1
Joined: Mon Nov 28, 2005 1:36 pm

sgvault_log.LDF is enormous

Post by koconnor » Mon Nov 28, 2005 1:50 pm

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
Posts: 3655
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Nov 28, 2005 2:05 pm

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.
Jeff Clausius
SourceGear

drmccue
Posts: 24
Joined: Thu Jun 21, 2007 3:21 pm

syntax clarification

Post by drmccue » Wed Dec 05, 2007 2:55 pm

The SQL syntax for the first step is:

BACKUP LOG sgvault WITH TRUNCATE_ONLY

jkp*74
Posts: 147
Joined: Wed Dec 15, 2004 9:42 pm
Contact:

Post by jkp*74 » Mon Jan 07, 2008 12:00 am

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 :? )
Joel
Micro Modular System
http://www.mmsis.com

jclausius
Posts: 3655
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Jan 07, 2008 8:47 am

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.
Jeff Clausius
SourceGear

Locked