Almost every developer knowns that the poor performance in many cases is due to poorly designed database or SQL queries
(for example, when the table does not have indices that the query can use or when the query uses unnecessary
performance killers such as ORDER BY/GROUP BY).
WordPress can provide only the list of the queries and the developer has to manually run every query and analyze it.
Very boring, isn’t it? SQLMon tries to help the developers and analyzes the query itself, reporting everything that needs attention.
Every query passed to WordPress is analyzed (using EXPLAIN) and the results are shown in the theme’s footer or Admin panel’s footer
(they are visible to site administrators only — this allows to use SQLMon even on live sites).
One of the key features of SQLMon is that it can run EXPLAIN not only on SELECT queries but also on UPDATE/DELETE and INSERT/REPLACE INTO … AS or
CREATE TABLE … AS.
The plugin is perfect for WordPress developers, plugin and theme authors and site administrators who are trying to find out why the blog is too slow.
IMPORTANT: the project has moved to Launchpad, please use it to report all bugs, suggest improvements,
request features and get the latest development version.
This plugins requires that PHP 5 be installed.
No support for ancient PHP 4, sorry.
SQLMon is incompatible with plugins that install their own
wp-content directory (DB Cache, DB Cache Reloaded, probably W3 Total Cache).
If you want to remove the plugin completely, please deactivate it first and make sure that
wp-content/db.php is deleted (if not, please delete it yourself).
Please use Launchpad to report any bugs.
sqlmonfolder to the
- Please make sure that
wp-contentdirectory is writable by your web server (when activated, SQLMon will copy
- Activate the plugin through the ‘Plugins’ menu in WordPress.
- If everything is fine, you will see
None yet. Be the first to ask.
- Applied jeremyclarke’s color scheme
- Bugs fixed: LP #628621
- Display how the optimizer qualifies table and column names in the SELECT statement, what the SELECT looks like after the application of rewriting and optimization rules, and other notes about the optimization process
- More details
- WordPress 3.1-alpha compatibility (LP #627209)
- CONNECT times are now also shown in the logs
- Removed forgotten unserialize()
- Code optimization. Got rid of EXPLAIN serialization.
- Added a check if wp-content/db.php exists before trying to remove it on deactivation (no errors are thrown if the file does not exist)
- Minor cleanups
- Minified CSS
- Major code refactoring
- Code cleanup
- Throws a warning when wp-content/db.php cannot be removed on plugin deactivation
- Does not cause the white screen of death when the plugin is removed and wp-content/db.php is not.
- Code cleanup
- Support for multiple databases
- First public avaliable version