As a trust we have had two instances of rapid db expansions filling up drive space. Once was a bug in the temp db, the second an error in Preproduction where dodgy code was running.
It would be nice if there was a more manual "Warn" value setting for big an expansion in x amount of time. I.e. If daily the db only grows 15gb usually then if the db grows bigger than this in a day a process should automatically write an alert level (user defined default of 2?) into the messages.log file.
I would call this something like "Expansion warn value" as a setting available on database propeties page.
Also a general "Warn Size" value could be set that while expansion would occur a flat value independant of OS to say if it reaches more that x bytes it logs a (1 or 2?) alert in messages.log
Thank you for submitting the idea. The status has been changed to "Future consideration".
Stay tuned!