On Tue, Mar 30, 2004 at 10:30:03AM -0800, Dathan Vance Pattishall wrote:
> Tips on managing very large tables for myISAM:
>
> 1) Ensure that the table type is not DYNAMIC but Fixed.
> => Issue the show table status command.
> => Look at Row Format
> => if Row Format != Dynamic the your ok
On 30 Mar 2004 at 10:30, Dathan Vance Pattishall wrote:
> 1) Ensure that the table type is not DYNAMIC but Fixed.
> => Issue the show table status command.
> => Look at Row Format
> => if Row Format != Dynamic the your ok else get rid of varchar type
> columns
> => Reason:
> Your myISA
Tips on managing very large tables for myISAM:
1) Ensure that the table type is not DYNAMIC but Fixed.
=> Issue the show table status command.
=> Look at Row Format
=> if Row Format != Dynamic the your ok else get rid of varchar type
columns
=> Reason:
Your myISAM table c
I did some tests with 20GB tables and several millions of rows a few months
back, and what helped improve the performance the most was to separate the
(small) columns used for searching from the (large) columns containing data.
My test table was from a messaging system, and I redesigned it so that
hi!
Chad Attermann wrote:
Hello,
I am trying to determine the best way to manage very large (MyISAM) tables, ensuring that they can be queried in reasonable amounts of time.
--8<
Why insisting in using myIsam, and not use some table format that can
assure you some degree of crash recovery a
