We continue to get this error now. It happens about once a week on a repository with "Quiet" logging enabled and about 10 active users. Questions:
1. How do I fix this for the time being?
2. How do I fix this so it never happens again?
We're using SQL Server v3.1.9 and SQL Server 2005 Enterprise Edition.
The transaction log for database 'sgvault' is full
Moderator: SourceGear
Check out this post and see if any of the suggestions help:
http://support.sourcegear.com/viewtopic.php?t=6202&
http://support.sourcegear.com/viewtopic.php?t=6202&