Contents
How to troubleshoot rapid growth in database and transaction log files?
(These registry values are not currently available in Exchange Server 2010) Check for any excessive ExCDO warning events related to appointments in the application log on the server. (Examples are 8230 or 8264 events). If recurrence meeting events are found, then try to regenerate calendar data server side via a process called POOF.
Why does a database grow at a rapid rate?
(As with new content creation in rapid log growth, we would expect the database to grow at a rapid rate with the transaction logs.) This is often referred to as database “bloat” or database “space leak”.
Why does my SQL server log keep growing?
You need to troubleshoot the main cause behind running the log operation for a long time, such as the internal blocking process or a performance issue on the underlying disk I/O system to overcome that log growth.
Why does SQL Server need a transaction log?
While taking a full backup of the database, SQL Server is unable to reuse the transaction log for the duration of the backup, even if the database is in SIMPLE recovery. If your database is very busy, or backups take a long period of time, this can require a large transaction log, even if the database is in SIMPLE recovery.
What to do if your log file is too big?
Another option is to create a new log file for the database on a different disk that has enough space by using the ALTER DATABASE YourDatabaseName ADD LOG FILE syntax. Once you have identified your problem and have been able to truncate your log file, you may need to shrink the file back to a manageable size.
How to stop rapid growth in outlook log files?
Launch Outlook to confirm the log file growth issue on the server. 2. If log growth is confirmed, do one of the following: Check users Outbox for any messages. If user is running in Cached mode, set the Outlook client to Work Offline. Doing this will help stop the message being sent in the outbox and sometimes causes the message to NDR.