{"id":1805,"date":"2014-01-12T11:00:13","date_gmt":"2014-01-12T16:00:13","guid":{"rendered":"http:\/\/sqlity.net\/en\/?p=1805"},"modified":"2014-11-13T13:46:13","modified_gmt":"2014-11-13T18:46:13","slug":"eight-reasons-transaction-log-files-keep-growing","status":"publish","type":"post","link":"https:\/\/sqlity.net\/en\/1805\/eight-reasons-transaction-log-files-keep-growing\/","title":{"rendered":"Eight Reasons why your Transaction Log Files keep growing"},"content":{"rendered":"
\n

Introduction<\/h3>\n

\nA while back I wrote a short article about the Transaction Log Reuse Wait<\/a>. Because it turned out to be very popular, I decided to follow up on that article and give a little more detail about the reasons why your database log files keep taking up more and more space.\n<\/p>\n

\nSQL Server itself actually tells us what is going on with the log files in the log_reuse_wait_desc<\/span> column of the sys.databases<\/span> catalog view. So, if you have a particular database that has a log growth problem, you can just run this query to find out more:\n<\/p>\n

\n[sql]\nSELECT D.name,
\n D.log_reuse_wait_desc
\nFROM sys.databases AS D;
\n[\/sql]\n<\/div>\n

However, this query just returns a keyword. To understand the cause of the different values of the log_reuse_wait_desc<\/span>, we need to dig a little deeper.\n<\/p>\n

Log Records<\/h3>\n

\nSQL Server uses the transaction log to guarantee the ACID properties, particularly the durability requirement. For every transaction, enough information to redo as well as undo that transaction it is written to the log file. Before any transaction can commit, SQL Server waits to get a confirmation from the hard drive that the log record was written successfully.\n<\/p>\n

\nThe transaction log gives SQL Server enough information to redo the operations that made up the transaction, should the actual change not make it into the data files, for example because of a crash. Because SQL Server has this information secured in the log file, it does not need to wait for the changes themselves being written to the data files and can commit the transaction while the data page changes still reside only in memory.\n<\/p>\n

\nEvery once in a while SQL Server will execute a checkpoint operation. During this operation data pages that were altered by previous or current transactions are written back to disk.\n<\/p>\n

\nAs a side note, it is possible for data pages containing changes of open transaction to be written to disk during a checkpoint. However, SQL Server has enough information in the transaction log to undo those changes, should the need arise. To have this flexibility SQL Server stores both the redo and the undo information in the log.\n<\/p>\n

Log Reuse<\/h3>\n

\nOnce every change to any data page that was executed by a single transaction was successfully saved to disk, the log record for that transaction is not needed anymore and its space in the log file can be reused.\n<\/p>\n

\nTo accommodate for reuse, SQL Server organizes the log files as a ring buffer of several containers called virtual log files. There is no direct way to influence their size and or number. SQL Server manages that automatically.\n<\/p>\n

\nThe virtual log files keep track of all their transaction log records and note if they are still needed, for example in an open transaction. Once all log records within a virtual log file are not used anymore, the virtual log file itself is marked as ready for reuse, and SQL Server will overwrite it with new log records once it gets around to that place in the ring buffer. The process of marking one or more virtual log files as reusable is called log truncation.\n<\/p>\n

Log Reuse Wait<\/h3>\n

\nThe above section described the general behavior of log reuse. There can however be several reasons for a log record to still be required by SQL Server for (potential) future operations. With that its virtual log file cannot be reused. If that happens for an extended period of time, SQL Server might run out of virtual log files and has to add additional ones. For that the physical file has to grow. If autogrowth is enabled for the log file and there is enough room on the drive this will happen automatically. If automatic growth is not possible, the database becomes effectively read-only, causing all write attempts to fail until the situation has been resolved.\n<\/p>\n

\nThe query shown at the beginning of this article allows us to find the most prevalent reason why virtual log files can't currently be reused. As of SQL Server 2012 it can return 10 different values:<\/p>\n