![]() If you don't need point in time recovery, which I can't imagine being the case for most production systems, but there are some out there, put the database in SIMPLE Recovery and the log will auto truncate unless you have a long running transaction. If you truncated it, so you could shrink it, resize it manually to control VLF counts, which impact performance, and to keep if from having to grow under load which will impact performance since the logs have to be zero initialized. If you are in FULL recovery, you have to backup the log, and you should be doing it frequently, likeĮvery 1-2 hours. The full log isn't the problem it is the symptom, the problem is one of the two mentioned items above. ![]() Or index rebuild that is filling the log. Either you aren't doing log backups (or they are not occuring frequently enough for the system demands), or if the database is not in FULL Recovery you have a long running transaction If your transaction log is growing, you have one of two problems. Truncating a log file breaks the log chain and impacts your ability to recover the system to a point in time. Shrinking a database data file results in index fragmentation. You have two different concepts confused. It might be a while before it evens itself out. What steps can I take to prevent this? How do I monitor the log files internal fragmentation as it grows? ElvUI/Tukui, Details, and Weakauras / Wago.io have been overloaded since the pre-patch launch with people trying to play and get addons. I read that one of the side effects of truncating and shrinking a large log file is that it will incurr fragmentation as it grows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |