I want a DBMS, but don't know which to select. Essentially, the applying makes many Place / UPDATE, but additionally many Choose. Choose mostly quite simple, one area only.

I'm using MySQL + InnoDB right now, but because the database keeps growing, I want the very best solution. The table can grow indefinitely, and also the time +- 2GiB


Will operate on Linux, and possibly rarely in FreeBSD. Not require a person management, all processes presently connect as root. Typically, you will find many synchronised accesses (now in 83 threads, based on the mysqladmin).

Access is going to be with C++, but need use of PHP also

PHPMyAdmin statistics:

choose: 42.57%

place: 7.97%

update: 49.45%


After a little thought, and also the solutions here, In my opinion which i can't use MySQL for the client library is GPL What other that doesn't harm (much) performance?

I believe you have ample options.

  • You can keep to make use of MySQL. YouTube used it fairly successfully
  • PostgreSQL (Free, Free, very good performance, reliable)
  • Oracle (NOT free, but has good support for large databases)

Whether it's quite simple queries, can it be done well having a key/value store?

I'd think MySQL is a superb choice from what you've mentioned. Oracle is not free, and it has some overhead in most the safety and enterprise level features that MySQL does not. You would like support for multiple languages. MySQL can scale well (In my opinion Flickr is a great one). Most databases are available via most languages: e.g. Perl, Java and C all have driver based APIs ( JDBC, DBI and ODBC ). IIRC PHP has one very similiar to DBI. Also: beginning having a database does permit you some wiggle room for future years: e.g. joins and aggregation.

One advice I'd give is: make certain whatever you decide is ACID compliant. Also, You may take time to compare PostGres and find out if there's something about this that meets your requirements too or much better than MySQL.

Based on this, the utmost database size on Linux 2.4+ (ext3) is 4TB. And So I think you're safe to stay with MySQL+InnoDB if performance is sufficient.