I've been fixing some issues lately where weekly maintenance has been causing logs to grow and filling disks.Is there any rule of thumb for allocating log space for doing reorgs and rebuilds in a worst case scenario? I'm thinking 3x the largest database size?I've been watching them run on databases in the range of 50GB where the logs are growing well over that for rebuilds or even reorgs. Once you have a few databases like this on a server, you can suddenly eat through a lot of disk space just for holding logs during maintenance. The standard seems to be to shrink logs after each part of the maintenance run but that feels a bit dodgy to me.
↧