Just a side note... you can do JOINs on tables from different databases on the same
mySQL server
eg
SELECT t1.UserName FROM db1.table AS t1, db2.anothertable AS t2 WHERE t1.UserName =
t2.UserName
As for database layout... I would go with what makes the most sense... If having 84
tables in one database makes sense then do
it... it wont really hurt performance until you start having hundreds of tables in one
db.
However, since you can do JOINs across databases (on same server) if it makes sense to
split your tables into multiple dbs... the do
it!!
BTW the limit for number of tables in one database is roughly 10,000 depending on your
OS (Linux running EXT2 among many others)
----- Original Message -----
From: "Richard Reina" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 05, 2001 7:40 AM
Subject: How many tables in a database?
> 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
---------------------------------------------------------------------
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
