Wm Mussatto wrote:
Assuming you are using MYISAM table types, each table requires at least
three files on the disk. If they are in one database they will all be in
one directory (how fast is your OS at finding the files in its directory
structure?).
Are they going to be opened at the same time
On Thu, May 24, 2007 2:12, Przemys?aw Klein said:
Wm Mussatto wrote:
Assuming you are using MYISAM table types, each table requires at least
three files on the disk. If they are in one database they will all be
in
one directory (how fast is your OS at finding the files in its directory
Martijn Tonies wrote:
Hi,
I'm working on quite big database. It consists of about 200 tables.
Additionaly about 50 tables are per year (because of annual data). It
means every year new 50 tables will have to appear in application. And
now I have a question. Should I use separate databases
On Tue, May 22, 2007 23:29, PrzemysÅaw Klein said:
Martijn Tonies wrote:
Hi,
I'm working on quite big database. It consists of about 200 tables.
Additionaly about 50 tables are per year (because of annual data). It
means every year new 50 tables will have to appear in application. And
now
Hi All.
I'm working on quite big database. It consists of about 200 tables.
Additionaly about 50 tables are per year (because of annual data). It
means every year new 50 tables will have to appear in application. And
now I have a question. Should I use separate databases for annual data
.
There are limitations to merge tables (i.e. can't be InnoDB), so you need to
read up on it to see if it will work for you.
- Original Message -
From: Przemysław Klein [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Tuesday, May 22, 2007 3:57 AM
Subject: design choice - quite many tables
Hi
Hi,
I'm working on quite big database. It consists of about 200 tables.
Additionaly about 50 tables are per year (because of annual data). It
means every year new 50 tables will have to appear in application. And
now I have a question. Should I use separate databases for annual data
(i.e.
