When trying to perform an action in the MessageStats console or while performing a gathering you receive an error message that includes the message "Error in Executing SQL Statement - Message: The transaction log for database 'MessageStats' is full"
In SQL Server the transaction log file is a fixed size file that starts out empty and fills up as transactions occur in the database. When creating a database along with the file location you can specify a minimum size to start the SQL Server transaction log file out with. This size is just the minimum starting point because as the database is used the transaction log will grow. If the transaction log file fills up and is not allowed to grow or can't grow due to disk free space no more transactions can be written to the database file.
The information provided here is known to work successfully; however, they have not been officially tested by Quest Software Quality Control. If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by Quest Software Support and Development. Quest Software Support and Development recommend to always make a backup of the current database prior to execution of any script(s) or actions that may modify it.
For customization of the MessageStats, please contact our Professional Services Organization: http://www.quest.com/professional-services/
Change the recovery model of the messagestats database to simple to reuse transaction logs. Transactions are still written to the transaction log, but once the transaction is complete and the data has been written to the data file transaction is cleared from the log file. Since this space is reused there is not the ability to do a point in time recovery of the database. You will only be able to recover the database up to the point of the last full backup of the database.
For more information, please see the Best Practices for maintaining the MessageStats SQL Database guide within the following Solution: