Free eBook: SQL Server Transaction Log Management

When a SQL Server database is operating smoothly and performing well, there is no need to be particularly aware of the transaction log, beyond ensuring that every database has an appropriate backup regime and restore plan in place. When things go wrong, however, a DBA's reputation depends on a deeper understanding of the transaction log, both what it does, and how it works.

Managing the SQL Server Transaction Log: Dealing with Explosive Log Growth

You've just become responsible for a database, only to find that the log file is growing out of control. Why is it happening and what do you do to correct it?

Why is my transaction log full?

Why does the transaction log fill up? There are a variety of reasons, and MVP Gail Shaw walks you through the various things to check.

Reading SQL Server's Transaction Log

This article shows how you can read the [RowLog Contents] in the Transaction Log, for Real!

Transcation Log space monitoring

This SP will monitor T-Log space and sends mail to DBA if log space usage is above threshold value

Clearing the Transaction Log

Shrinking the transaction log

Managing Transaction Logs in SQL Server

The Transaction Log provides the means by which either the complete set of tasks of a database transaction are performed or none of them are. It ensures that , via rollback, only valid data is written out to the database, and it allows transactions to be played back to recreate the system state right before a failure. Robert Sheldon explains the various basic tasks involved in managing the transaction log.

Determining the source of full transaction logs

Many DBAs at some point have had to deal with a full transaction log. Check out these steps for finding the cause to quickly solve the problem.

Full Transaction log

One of the common questions often asked online is how to respond to a full transaction log. New author Krishna Potlakayala brings us a few techniques for dealing with this.