SQL Transaction log drive out of space worst case senerio....
Posted on 2006-05-04
Just doing some research on worst case senerio for a question that my boss asked of me. I have a SQL db that gets hit hard every once in a while and the transcation log grows rapidly. I've got a script that shrinks the log three times a week which I might increase in frequency. The problem is that the drive the trans log is on, is relative small (10GB), Although I'm getting more space for this drive in a couple of months once we bring our new SAN online. Until then I'm stuck with what I have for space at the moment (As a side note, the DB and trans logs are on different drives).
So, in a worst case senerio, what would happen to the SQL DB if the transaction log grows and fills the drive completely? In other words, the trans log grew to full drive capacity and ran out of space and couldn't grow anymore but the server was still getting hit with transactions and know was around to mannually shrink the log in time. For the sake of argument, lets saying drive space alerting failed to notifiy people or no one could respond fast enough to shrink the log.
Is the DB going to crash hard or will SQL just stop processing requests until the log is shrunk?