Simple recovery model will keep the Tx log small as it will essentially
truncate when a checkpoint occurs, see
http://msdn.microsoft.com/en-us/library/aa173531(SQL.80).aspx . But if it is
already large i.e. your 27GB you need to also run DBCC ShrinkDatabase after you
switch it. That will
Thanks Paul,
This turned out quite different, it was open transaction which happened
during nightly backup which locked the database. So checkpoint was not
happening and auto truncate of log not happening as well.
Interesting thing that within 15 hours of locked/open transaction log grew
to 27
