SQL Server Transaction logs grow infinitely Allowing the SQL Server transactions logs for the MailSite database grow to an unmanageable size may cause the SQL server to become unavailable. This can cause MailSite services to become unavailable or behave abnormally as the MailSite cannot connect to SQL Server.

In such situations you may see the MailSite services in a 'paused' mode or 'pending' mode. MailSite has the ability to suspend the services if the SQL server becomes unavailable. The services are not however designed to handle poor SQL server management.

Your DBA should already have management policies put in place to handle the Transaction log. Your DBA is the best resource to setup rules for SQL Server management in accordance with your company disaster/recovery procedures. Support for SQL server management is beyond standard MailSite support. Typically the recovery model for the MailSite can be set to Simple, rather than Full given the nature of the data stored. If you must set it to Full, then backups should be scheduled to help keep the transaction log at a manageable size and to ensure SQL server will function correctly. More information can be found at following Microsoft article, or by contacting your Database Administrator.