Partitioning mySQL tables that has foreign keys?

Question

What would be an appropriate way to do this, since mySQL obviously doesnt enjoy this. To leave either partitioning or the foreign keys out from the database design would not

Answer 1

I would strongly suggest sharding using Date as the key for archiving data to archive tables. If you need to report off multiple archive tables, you can use Views, or build the logic into your application.

However, with a properly structured DB, you should be able to handle tens of millions of rows in a table before partitioning, or sharding is really needed.