|
|
FYI: there is already a new UI for v2026 (per 0021652 ) , so I would rather solve it with target 2026 so that it can be tested through beta testing circle image.png (38,756 bytes) |
|
|
Because 'Optimize database' is quite fast task (usually takes less time than the actual backup where compressing part takes the most) then I would still prefer to Optimize before backup, so probably just a new checkbox [x] Optimize database before backup .. BUT this could imply that just the DB that is backed up is optimized So cleaner approach would be to separate it from backup (like suggested by Rusty) and add the scheduled maintenance, but in that case I believe that 'Optimize database' is the only task that should be scheduled for maintenance. Idealy if MM could self-detect that DB needs to be optimized and suggested to the user the optimization. The detection could be based on total amount of tracks in DB versus overal DB size. Maybe if DB size is over 2GB and the total amount of tracks is less than 100K as a treshold for optimization? |
- Anonymous
