Re: Partitioning & Tablespace
> for large data MySQL
If you don't have at least a million rows, you should (probably) ignore everything having to do with tablespaces and partitions.
innodb_file_per_table = YES
is recommended in general. It's trivial to set; it can have distinct benefits later; there are virtually no downsides.
In some use cases, PARTITION is an excellent choice. Unfortunately, many people new to MySQL see PARTITION as a panacea for performance. Please describe your data and your application. Perhaps PARTITION will be quite beneficial; perhaps it will be a waste of effort.
Subject
Views
Written By
Posted
4685
May 29, 2011 10:13AM
1918
May 31, 2011 03:40PM
1718
May 31, 2011 07:58PM
2514
June 01, 2011 03:57AM
Re: Partitioning & Tablespace
2106
June 01, 2011 07:34PM
1855
June 02, 2011 12:43AM
1732
June 02, 2011 01:02PM
2025
June 02, 2011 07:19PM
1592
June 02, 2011 08:44PM
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.