I have several databases that, despite being backed up regularly, do not release space to the operating system. In one extreme case, I have a log file that is less than 1% utilized (and has been for months.)
I know how to manually force a shrink, but I should not need to do that on any sort of regular basis. In fact, it is against best practices to manually shrink a log file (or any database file for that matter) because of the very high risk of an unrecoverable
It is my understanding that SQL Server will eventually handle these things on its own. However, it does not appear to be doing so. Any thoughts as to why?
View Complete Post