hi!
I'm going to be building a system that will need to handle a fair bit of
data...
Basically I have tables that will eventually have millions of rows of
data, I believe I need to split them up for 2 reasons, 1, performance
(the tables will be quite active), 2, if a table get's corrupted then it
can be repaired much faster and the whole system isn't affected.
I'm sure others have come accross this, if anyone can point to some
mysql features, or other docs that would be great.
I'm guessing though, that I need to do this at the application level.
Unless mysql has table partitioning? In the past I've done stuff like
having a user table with a mail_table_id, the mail_table_id holds tells
which table that users mail is stored in, and every once in a while I'll
manually tell the application to start assiging new users to use a new
table.
I'm thinking perhaps a better way would be too have a user table with an
auto increment id and creating 10 tables named mail_0, mail_1, etc...
and taking the last digit of the user id to say what table id their mail
is stored in. so that the 10 tables would be evenly used.
Would table partition be hard to implement in mysql? I've run into
this situation a fair number of time, and useing the mail_table_id way
work fine, but I feel this should be handled by the database.
anyhow, thanks for any thoughts!
Tom
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
