Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Developers require database access to a significant number of databases, each with 220+ tables, and currently they are provided this using phpMyAdmin Initial load is very slow, puts some load on the database cluster beneath, and runs lots of (needless) SHOW TABLES FROM x queries to gather data for every table in every datbase. Developers do not require this information in the left hand navigation pane, however this information is still required when they select that database.

There are various options available for configuring the installation, however none of them are obviously tailored to handle a colossal number of databases.

  1. Can anybody recommend options on tuning phpMyAdmin to deal with many tables ($cfg['ShowStats'] = false; is the only obvious one)?

  2. Is there any equivalent to phpMyAdmin tailored to very large deployments? Perhaps caching table meta data (there are memcached instances available) or not outputting such verbose information?

  3. Does phpMyAdmin suffer the same sluggish performance? Upgrading is a possibility.

share|improve this question
up vote 2 down vote accepted

I would investigate upgrading to There are a number of enhancements to the selects and being able to turn features on or off. Here's one I would look at as well as creating some custom selects in ShowDatabasesCommand

However requires PHP 5.2 or better and Mysql 5.0.15 or better.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.