title: mysql - table partitioning vs "manual" table partitioning
body: <p>I have the following choice:</p>
  
  <p>I have a huge table (9999999999999 rows), let's call it tableHuge, and I would like to split it into multiple tables (to optimize queries). This table contains dates (days of the month), and most queries are made using a specified month as search key in select. This leads me to the following choices:</p>
  
  <p>Choice one:
  Split the table into multiple tables, using a month as his tail (like lessHugeTable_01, lessHugeTable_02, etc.). Then I can take care in my app to access table that I need. The main downside is loosing the ability to join, in cases that includes more than one month (or join with an union... well.. complications).</p>
  
  <p>Choice two:
  Use table partitioning.</p>
  
  <p>Since I never used partitioning before (so I don't have knowledge to compare), I would like some advice on how to do it, pros and cons if possible (except obvious things like "if your manual partition table gets broken you loose only that data while in table part you loose whole data").</p>
  
  <p>Thank you for your time.</p>