Jeff Moden (10/26/2016)
Siberian Khatru (10/26/2016)I'm kind of torn here as to whether or not to bother other than to switch to SIMPLE. I would guess at this point that leaving the log files as is after being switched to SIMPLE recovery model would not be harmful as an alternative to screwing with it too much, especially since it will be migrated after a while.
Most folks will certainly recommend just leaving the log files as they are. I'll say "It Depends" and now may be a great opportunity to fix some previous sins especially if the log files were original built using the SQL Server defaults.
You might be able to get a bit of a performance increase if you rebuilt the logs with more sane settings. The BIG thing is planning for the inevitable... the need for an urgent restore even if it's not point-in-time. Even "instant file initialization" won't help in the area of log files during a restore. They shouldn't be overly large and they shouldn't have the bazillion VLFs that the default settings create. Both slow restores down a lot.
You could write a script to rip through all the databases to do this at the same time that it sets the databases to SIMPLE.
Good points. I am going to do the switch first (in the midst of that actually) and then come back through once I have an idea how these logs are used. remember, they have been untouched for YEARS so who knows right now. I look at this as a learning opportunity 🙂