oooo bad, bad, bad set-up.

The database is in FULL recovery mode which requires the logs to be backed up if SQL Server is going to shrink them. Since logs aren't being backed up, they grow huge. So the database is set in SIMPLE mode and the log shrunk. Then it's put back in FULL recovery mode again.

That's a total waste. If you aren't going to do log backups, just put the database in SIMPLE mode and leave it there. SQL Server will CHECKPOINT the log file and free up space as it goes.

Things to consider: SIMPLE mode does NOT allow you to recover to a point-in-time. You can only recover to the last full backup made. If you can't afford to lose data, leave it in FULL mode, start doing log backups (BACKUP LOG command), and get rid of the switch to SIMPLE and truncating/shrinking the log file.

-SQLBill