Re: How many tables in a database?

2001-02-09 Thread Kissandrakis S. George

I have 6500 tables under one database there is no problem
i hope that helps :)

-- 
Kissandrakis S. George [[EMAIL PROTECTED]]
Network and System Administrator   [http://www.phaistosnetworks.gr/]
Tel/Fax: (+30 892) 24450/23206
Phaistos Networks S.A. - A DOL Digital Company

-
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




Antwort: Re: How many tables in a database?

2001-02-09 Thread alexander . skwar



On 09.02.2001 12:01:01 Kissandrakis S. George wrote:

 I have 6500 tables under one database there is no problem

Pardon me, but how do you keep track of that many tables?  I mean, I've a hard
time with 10 or 20 tables - but 6500???



-
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




Re: How many tables in a database?

2001-02-07 Thread Jan Dvorak

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




Re: How many tables in a database?

2001-02-06 Thread hooker

 
 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

Richard, I'm not sure about right or wrong ways ... but I've got a 
system which creates two tables per day, keeps 60 days worth of data
in the current database, and rolls tables off the end into a history
database every night.

The current database actually has about 150 tables in it (there are
quite a few which stay in place). Realistically, the server won't
support queries over 60 tables (and who's surprised?), so I've got
scripts which do nightly summaries which get dropped into extra
tables. It might sound a little clumsy, but having tried Perl scripts
which prepare and select on 60 tables to answer a query, for performance
reasons, summary tables are the way to go.

Occasionally, the system *does* get queries on about 50% of the
available tables, but the users are made aware that it won't be fast !

Hope this helps a little.

Regards,

Paul Wilson
Senior Programmer, iinet Ltd

-
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




Re: How many tables in a database?

2001-02-06 Thread Jason Terry

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