Ratheesh K J wrote:
Helo all,
Just wanted to know when should a Table be considered for partitioning ( or
should it be archiving ).
Almost all of our tables are of Innodb type. I am looking for an estimate rather than a
"Depends on situation" kind of an answer.
We have few of our table swhich are very huge ( in terms of number of rows ), > 70 lac rows. Should this be a factor for table partitioning or should the actual data size be a factor.
1) In that case for a system with 80 GB reserved for MySQL when should we worry
about Table sizes?
Partitioning helps queries across sections of those tables, it doesn't
change "table size".
If you have a table with a "year" column you could break it down into
months, so when you query a particular month, the whole table isn't
checked, only a particular "partition".
So mysql can go to the right partition (month), then use appropriate
indexes to find the relevant records.
Without partitioning, the whole table index has to be evaluated.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
