Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

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!

0 votes



One answer

Permanent link
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.

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 82
× 15

Question asked: Jan 26 '16, 5:12 p.m.

Question was seen: 3,794 times

Last updated: Jan 26 '16, 6:14 p.m.

Confirmation Cancel Confirm