I'm not sure if you have a problem with one large InnoDB table or one
large file. With InnoDB you can specify multiple files, limit the size
of each file and even specify the location of each file. So you could
limit your InnoDB files to say 1GB each (or lower/higher) and specify
which disk
Hi All,
I tried digging for this information in the archives but could not
find anything.
I am in to developing an app. that uses very high amount of data
(Close to 80 GB per machine). It has 3-4 logical tables. But I have to
partition them in to multiple tables because the mysql table size
If you are hitting file size limits, you probably want to look into
using the InnoDB table type. That will allow you to work around file
size limits and have a database of just about any size you need. You
won't end up having a 30GB file, but multiple smaller files which will
be transparent to
Hello.
Think about merge storage.
http://dev.mysql.com/doc/mysql/en/MERGE_storage_engine.html
Alok Gore [EMAIL PROTECTED] wrote:
Hi All,
I tried digging for this information in the archives but could not
find anything.
I am in to developing an app. that uses very high amount
Thanks a lot for the quick response :)
We are not using MyISAM tables. All our tables are
InnoDB tables. The rational behind this decision is
that the database is expected to get hundreds of
insert queries per second, so we want the row level
locking
of InnoDB to speed this up. (I should
