We have a SQL2008 instance in an old server that we're not ready to migrate. Hard disk space is an issue on that server. That DB is on Simple recovery model and it holds data related to VMWare. I'm not sure what data it holds, but, the VMWare administrator told me Simple recovery model with nightly full backup is more than sufficient.
With hard disk space being an issue, I set the maximum log file autogrowth to not exceed the hard disk space. That creates an alert on a daily basis; almost every time during the night from SCOM.
From this article (https://technet.microsoft.com/en-us/library/ms178037%28v=sql.105%29.aspx), and I quote "truncation occurs automatically under the simple recovery model when database is backed up". So, in my case, the log will truncate in the evening when the full backup is ran.
I realize shrinking the log file just caused it to autogrow when it needs to. And that'll be an increase to the i/o and performance.
Is this a good example where shrinking log file is a good idea? Or for that matter, setting autoshrink for the DB properties?
IF not, how would you guys handle the issue(s) - hard disk constraint, and log file autogrow size causing SCOM alerts?