depending on your board, 10MB could be used up in only a few posts.wmtipton wrote:meh.AmigoJack wrote:OPTIMIZE TABLE is hazardous - the documentation is quite clear about this: if you have a huge table it can also totally halt your whole MySQL DBMS when running out of disk space during this operation.
Obviously nobody knows or cares about this.
Mine are small. I wouldnt let any database get above 10MB or so anyway...not real need to for the sites I own or webmaster.
Takes about 3 seconds tops.
Most of these boards are for temporary material that gets deleted/pruned after so long.Lumpy Burgertushie wrote: depending on your board, 10MB could be used up in only a few posts.
that is an extremely small number to try to limit database size to.
It did dawn on me after reading some of the points made that maybe I really dont need to worry about it. I didnt realize that the overhead didnt just keep growing perpetually. I thought it would just keep getting larger and larger until what might be a 2MB database would end up being 10MB or so, which would be entirely unacceptable.Oyabun1 wrote:Since you are using less than 1% of the available database space there doesn't seem to be any need to optimise the database and with small databases you are unlikely to see any benefit from doing so.
You should make sure you backup the database before making any changes, including an optimisation, because as AmigoJack said there is a risk.
Not sure of the difference.Oleg wrote:Database overhead does not affect the size of dumps as it only exists in internal database structures.
If you are backing up data for its content as opposed to performing a system-wide backup of everything, you should always dump databases instead of backing up their raw files.
Thats interesting. I may have just assumed otherwise. I'll have to definitely check it out because if thats the case then theres no real need for me to bother with optimizing unless its for a specific reason.Oyabun1 wrote:The phpBB backup and restore drops the existing tables and recreates them, so any overhead in the tables is eliminated.