User requirements for MySQL Partitioning
Listed below are the required features to manage >1TB VLDBs:
- Global index on the primary table (across partitions)
- Local indexes on each partitions.
- Select fld1,... from <PrimaryTable>.<PartitionName> WHERE ....
- sqldump : dump entire table or selected partitions
- import entire table or selected partitions.
- Move partition from one tablespace to another/new.
- Merge,split , rename,truncate and drop partitions. Also set status to active or inactive.
- Option to load any partition to cache (heap storage engine may not help)
- Able to create view on a set of selected partitions.
- Optimization hints for Index usage and other select / join operations.
- Don't allow to drop all the partitions. Atleast the table must have one active partition.
- Row counts are cached for each partitions and for the entire table so that
the select count(*) from <table>.<partition> will display the count faster.
Regards..
Jey Razack
Subject
Views
Written By
Posted
User requirements for MySQL Partitioning
4320
May 25, 2005 11:11AM
3438
May 25, 2005 12:07PM
3025
May 26, 2005 01:33AM
3292
May 27, 2005 09:46AM
2941
May 27, 2005 12:57PM
2827
May 30, 2005 03:37AM
2699
May 30, 2005 11:09AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.