I think 12 tables is not a large number by any means.
If they _logically_ form one database, I'd not bother about the number.
Only if performance problems pop up, and are positively recognized as being caused
by too many files in the database directory, I'd start looking for a solution.
Which need not mean splitting the database up.
Why not look for a better-suited filesystem?
ReiserFS can handle huge directories without performance loss.
Jan
Richard Reina wrote:
>
> How do you decide when a table should go into another database. For
> example, I have a database with about 12 tables and growing. I keep
> them in one database because I am doing joins that periodically involve
> all of the tables. Is this the right way to do it?
>
> Richard
---------------------------------------------------------------------
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
