Tom.Thomson (10/17/2010)
(with some risk that the situation will deteriorate further, so that the transaction can't be rolled back or committed because there isn't space to log that action) or roll the transactiopn back now, as Gail suggested - but that too may not work if there isn't enough space on the disc to do it.
A transaction can always be rolled back. SQL always reserves enough log space when it performs operations for a rollback should it be necessary.
This has to be like this, as otherwise a full transaction log would almost certainly result in a suspect database if space was not reserved for rollback
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability