Classic fool who has default Full Backup model and out-of-control log file ---- how to I get this controlled? Hey there I'm usually more of a development dba but the old dba left --- and he left about a year ago without a replacement.
I'm finally actually looking under the hood of some of these servers -- I'm not a production dba but I ran some diagnostics I found online and they say I have big problems.
Anyway I'm learning this stuff slowly but this seems like a common issue --- I have Full Recovery mode on a particular database, but never back it up -- as a result the log file grows exponentially -- I take it?
What are my options to get rid of this?
I'm guessing:

If I do a full back up or schedule one, the log file will get cleared after this?

Can I just change to the simple recovery model? I know that has recovery implications - I'm comfortable with data loss as this is a BI database. Will that flush out the log file immediately as well? Do I have to do anything OTHER than a switch to the simple recovery model?


Is there some way to monitor the progress of either of these two options? I'm guessing either will cause the database to start chugging resources doing something or other.
Thanks!
Do I have to do anything OTHER than a switch to the simple recovery model?

If you have a full backup, and don't need point-in-time recovery, simply switch the database to Simple recovery.  After the next Checkpoint you should be able to shrink the log file.  If the active VLF happens to be at the end of the file, rebuild an index or two, and try again.