Problem with MySQL Big Database

[Nick name]

Hello,

I am creating a Database Architecture and there is a volume problem
with MySQL.

My tables are quite simple. Problem is they will record million of
lines.
Within 10 seconds, MySQL could receive 1.000 querries to insert raws in
the same table.

After 30 days, a table could be a 30.000.000 lines table.

I see several problems :
1. multi-querries at the same time
2. very high volume of database
3. recognition scripts and browse within results will be too long.

I think of having researched and developped multi-threading querries to
MySQL and back-tables that receive cut/paste from the main table.

I hope you had the chance to work with important volume, in order for
me to listen and work on the development of advised solutions.

I thank you for Your response,

Sophie
Ref : EC

[Markus Popp]

Hi,

with such big tables, Clustering and Replication might be an interesting
topic to get rid of it:

http://dev.mysql.com/doc/refman/5.0/en/ndbcluster.html
http://dev.mysql.com/doc/refman/5.0/en/replication.html

Markus

[Nick name]

Hi,

If I had the time, I would love to forget databases, using pure
zipped-txt.

Clustering and Replication sounds to me the exact answer.

Thing is the current developper (SQL&Web) that develop our galery does
not like embedded solutions.

I precisely need an expert to propose+redraw a volume SQL Architecture.

Regards,

Sophie.

Hi,

with such big tables, Clustering and Replication might be an interesting
topic to get rid of it:

http://dev.mysql.com/doc/refman/5.0/en/ndbcluster.html
http://dev.mysql.com/doc/refman/5.0/en/replication.html

Markus