I tried to reply to the topic listed above (http://support.sourcegear.com/viewtopic ... ction+logs), but it was a Gold Support Forum and I don't have access to reply to it.
We're using Vault 3.1.8.3771 and we are also seeing problems with a full transaction log. After discovering it, we recently changed the database from Full to Simple recovery mode and increased the max log file size to 2gb but the transaction log still filled up. We've also noticed that the tblcheckoutlistitems table has over 1.7 million rows. Any idea what may be causing this?
Thanks,
Laurie
Multiple transactions are written to the t-log of the DB.
Moderator: SourceGear
First on the large log issues, you can truncate the current logs and see if they continue to have problems with growing.
First, run backups:
BACKUP DATABASE { database_name | @database_name_var }
TO < backup_device > [ ,...n ]
Truncating the transaction log:
BACKUP LOG { database_name | @database_name_var }
{
[ WITH
{ NO_LOG | TRUNCATE_ONLY } ]
backup the log so the unused portion is removed ( BACKUP LOG command) and then run the following:
USE sgvault
GO
DBCC SHRINKFILE ( sgvault_log )
GO
First, run backups:
BACKUP DATABASE { database_name | @database_name_var }
TO < backup_device > [ ,...n ]
Truncating the transaction log:
BACKUP LOG { database_name | @database_name_var }
{
[ WITH
{ NO_LOG | TRUNCATE_ONLY } ]
backup the log so the unused portion is removed ( BACKUP LOG command) and then run the following:
USE sgvault
GO
DBCC SHRINKFILE ( sgvault_log )
GO
Everytime someone does a checkout, a checkoutlist is created. Each checkoutlist has a list of all the items checked out.
A Checkoutlist stays in the database for 5 days (default), after which it is deleted. You can have thousands of checkoutlists. (We are making this much more efficient in the next Vault release, BTW)
It's possible to have millions of checkoutlist items if users did large checkouts and/or if the checkoutlists are not being cleaned up for some reason.
This eventually could resolve itself as the the checkoutlists from the big checkout get deleted. However, if the delete transaction doesn't complete (because the transaction log is filling up, for example), there's a backlog of checkoutlists and Vault keeps trying over and over to delete the checkoutlists.
If you continue to experience problems with this, email support at SourceGear.com attn Linda and we'll send you some queries to narrow down the problem.
A Checkoutlist stays in the database for 5 days (default), after which it is deleted. You can have thousands of checkoutlists. (We are making this much more efficient in the next Vault release, BTW)
It's possible to have millions of checkoutlist items if users did large checkouts and/or if the checkoutlists are not being cleaned up for some reason.
This eventually could resolve itself as the the checkoutlists from the big checkout get deleted. However, if the delete transaction doesn't complete (because the transaction log is filling up, for example), there's a backlog of checkoutlists and Vault keeps trying over and over to delete the checkoutlists.
If you continue to experience problems with this, email support at SourceGear.com attn Linda and we'll send you some queries to narrow down the problem.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager