It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,878
×4,715
×82
×24
×15

question asked: Jan 26 '16, 5:12 p.m.
question was seen: 3,758 times
last updated: Jan 26 '16, 6:14 p.m.

Related questions

SQL Server Transaction Logs are HUGE

0
Dave Evans (148●1●28●46) | asked Jan 26 '16, 5:12 p.m.
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!

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●6●14) | answered Jan 26 '16, 6:14 p.m.
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.

Your answer

Register or 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.