SQL Server Transaction Logs are HUGE
Greetings,
We are wondering why our transaction logs for RTC are so gigantic. We are using the "Full" recovery model, with full backups each Sunday evening. The transaction logs are backed up hourly. How would you explain a transaction log of 135 GB with a full database size of 330 GB? And what size should we trim the log to?
Thanks for any help or insight!
We are wondering why our transaction logs for RTC are so gigantic. We are using the "Full" recovery model, with full backups each Sunday evening. The transaction logs are backed up hourly. How would you explain a transaction log of 135 GB with a full database size of 330 GB? And what size should we trim the log to?
Thanks for any help or insight!
One answer
File size alone does not mean much, unless it keeps growing. Check the document for transaction logs.
https://msdn.microsoft.com/en-AU/library/ms190925.aspx
Two points to note:
1. A copy-only log backup does not trigger transaction log truncation.
2. Truncation does NOT reduce the size of the physical log file.
https://msdn.microsoft.com/en-AU/library/ms190925.aspx
Two points to note:
1. A copy-only log backup does not trigger transaction log truncation.
2. Truncation does NOT reduce the size of the physical log file.