Chapter 7: Dealing with Excessive Log Growth
This chapter will examine the most common problems and forms of mismanagement that lead to excessive growth of the transaction log, including:
FULLrecovery model, without taking log backups
Of course, if growth is left unchecked, the log file may expand until it devours all of the available disk space or the maximum size specified for the log file, at which point you'll receive the infamous 9002 (transaction log full) error, and the database will become read-only. This chapter will cover the correct ways to respond to runaway log growth and ...