I have a a couple of SQL databases that collect website log files, replicate them to another location, and then flush out the older records every often, so there are a lot of transactions. The log files are set to unresticted size and grow to several times larger than the database files themselves. Every so often we need to shrink the log files and they will also release back 99% of their space.
The databases are configured for simple recovery model and they are not backed up (not deemed critial data). I am not very experienced with SQL and looking for suggestions/best practices on how to handle the situation. Should we schedule a nigthly job to shink the log files? Would scheduling a backup job (though not for the purpose of recovery) commit the log files to the MDF files and essentially clear them out? Any other suggestions?