>From the MySQL manual:
---
OPTIMIZE TABLE should be used if you have deleted a large part of a
table or if you have made many changes to a table with variable-length
rows (tables that have VARCHAR, VARBINARY, BLOB, or TEXT columns).
Deleted rows are maintained in a linked list and subsequent INSE
On 4/1/07, Bastien Koert <[EMAIL PROTECTED]> wrote:
I would say no, due to the overhead. What I would recommned is setting
that
up as a cron task and running it on a scheduled basis, usually when the
server is liightly loaded. Monitor the server and pick an optimal time.
This
is the same for all
I would say no, due to the overhead. What I would recommned is setting that
up as a cron task and running it on a scheduled basis, usually when the
server is liightly loaded. Monitor the server and pick an optimal time. This
is the same for all server mainenance type situations like index monito
Hello group,
I just have a quick question for you all. Here is it... Is it advisable to
run optimize table after each deletion of a record?
Thanks in advance,
Anna Vester
