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 Fo
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
how the
primary key is created and used.
/Henrik
-Original Message-
From: Chad Attermann [mailto:[EMAIL PROTECTED]
Sent: den 30 mars 2004 19:42
To: [EMAIL PROTECTED]
Subject: Managing Very Large Tables
Hello,
I am trying to determine the best way to manage very large (MyISAM) tables
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
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. One table in particular has
over 18 million records (8GB data) and is growing by more than 150K records per day,
and that rate is increasing. Bes
