I'm trying to figure out how to set up the storage for a site that currently requires only one server, but will certainly grow to demand more. I the database is largely innodb tables. I understand that clustering servers isn't an option because that ignores foreign keys. I saw reference to federated storage, but that seems to have issues too. Do you have any other storage suggestions that are compatible with foreign keys, and know the pros and cons? Thanks for the help.


  • What's a bc and an fk? – John Gardeniers Aug 28 '09 at 22:07
  • because and foreign key? – Mark Aug 28 '09 at 22:34
  • haha, yes. because & foreign key – storm Aug 28 '09 at 23:38
  • I edited the post and expanded the abbreviations so everyone can better understand the question. ;-) – KPWINC Aug 29 '09 at 0:44

(source: oreilly.com)

The book above is a very good place to start reading about mySQL and its various storage engines as well as the pros and cons of each.


  • ok, thanks. im going to go pick this up asap, and try to fully understand cagenut's suggestion. – storm Aug 28 '09 at 23:39
  • The book will help you A LOT. You can also find/purchase it online in .PDF format I believe. – KPWINC Aug 29 '09 at 0:45

short answer: 4 -8 spindles, 10krpm or above, raid10 w/BBU and write-back enabled

long answer: read the book and the website

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.