OpenLDAP includes a driver that allows it to store and access data held in MySQL Cluster. It uses the NDB-API to access the database and so the performance is extremely good. One of the great things about the solution is that it lets you simultaneously access the same data through both LDAP and SQL (or the NDB-API or any of the MySQL connectors). This article gives an example of how this can be done.
Database Recovery For MySQL is recovery software to recover MySQL database files. It supports MySQL .myd and .myi files. It is the ultimate read-only tool, which uses advanced algorithms to recover the corrupted database files and offers optimum disaster recovery for database administrators, business users, database programmers and more.MySQL database repair tool to recover and repair corrupted database generated through SQL.
A quick look at some strong points between InnoDB Hot Backup and Xtrabackup
Shlomi shows a real world scenario where the naive approach to monitoring fails spectacularly.
In my old post there is a bug when run in MySQL 5.1.30 and old, because the status variable Queries was added in MySQL 5.1.31. So i change to choose between Queries and Questions status variables, and I think the Queries represent more accurate result.
Sheeri explains, in practice, how to synchronize schemas using MySQL Workbench
Sheeri explains why turning on the query cache without thinking about the consequences is bad but also why simple benchmarks proving 'the query cache is bad' may be skewed
Maximize your strengths, minimize your weaknesses.
You can apply this approach to many things in life, I apply it to describing and using MySQL the product, and it’s components. The Query Cache like many features in MySQL, and indeed features in many different RDBMS products (don’t get me started on Oracle *features*) have relative benefits. In one context it can be seen as ineffective, or even detrimental to your performance, however it’s course grain nature makes it both trivial to disable dynamically (SET GLOBAL query_cache_size=0;), and also easy to get basic statistics on current performance (SHOW GLOBAL STATUS LIKE ‘QCache%’;) to determine effectiveness and action appropriately.
Mark Callaghan tests the query cache.
"The query cache has had an interesting history with MySQL. I don't have much experience with it. I might want to use it in the future so I enabled it during a run of sysbench readonly on an 8-core server. The results are fascinating."
Informative post about backup and restore procedures, disaster recovery plans and load balancing tips.
Install isolated side-by-side MySQL instances right the first time with this time-saving virtual manager.
Jeremy Zawodny tests MySQL Sandbox with a thorough description.
Giuseppe Maxia speaks at the April 2009 Los Angeles MySQL User Group about MySQL Sandbox and how to use it for simple and complex sandbox scenarios.
SPIDER Storage Engine: Database Sharding by Storage Engine
by Kentoku SHIBA (ST Global.,Inc)
The official conference page is at
Download the presentation file (zip archive) at http://assets.en.oreilly.com/1/event/21/SPIDER%20Storage%20Engine_%20Database%20Sharding%20by%20Storage%20Engine%20Presentation.zip
Presented at the April 2009 Los Angeles MySQL User Group (see http://www.meetup.com/lamysql/calendar/9882984/ for more details)
Andrew Aksyonoff is a Russian geek who created Sphinx back in 2001 and has been working on the code base ever since. Fluent in C++, less so in human speak, but keeps trying.
He lives in Russia.
Just how do you implement keyword search through that 10-million-row InnoDB table? Meet Sphinx, a blazing fast open source engine that makes it a breeze. We'll talk about what it is, how it works, and when and why use it.
Meetup search is powered by Sphinx.
The Boston MySQL User Group got Keith Murphy to speak at the June User Group meeting, about backups. Direct play the video at:http://technocation.org/node/559/playDirect download the video (351 MB) at:http://technocation.org/node/559/downloadLinks referred to in the presentation:MyLVMBackup by
Presented at MySQL Camp 2009 by Ewen Fortune of Percona.
XtraDB is a storage engine for MySQL based on the InnoDB storage engine, designed
to better scale on modern hardware, and including a variety of other features useful in high performance environments. It is fully backwards compatible, and so can be used as a drop-in replacement for standard InnoDB.
XtraDB includes all of InnoDBs robust, reliable ACID-compliant design and advanced MVCC architecture, and builds on that solid foundation with more features, more tunability, more metrics, and more scalability. In
particular, it is designed to scale better on many cores, to use memory more efficiently, and to be more convenient and useful. The new features are especially designed to alleviate some of InnoDBs limitations. We will talk about current status of XtraDB and directions of development.
Optimizing MySQL Performance with ZFS by
Allan Packer (Sun Microsystems), Neelakanth Nadgir (Sun Microsystems)
The official conference page is at http://www.mysqlconf.com/mysql2009/public/schedule/detail/7121 which includes the description
presented at MySQL Camp 2009.
Giuseppe Maxia and Sheeri K. Cabral give an introduction to what MySQL is.
A PDF of the slides can be downloaded at http://technocation.org/files/doc/2009_04_Tour.pdf (21 Mb).
Links referred to in the presentation, or related to the presentation:
The MySQL forge can be found at http://forge.mysql.com, which contains the Wiki (http://forge.mysql.com/wiki) as well as the worklog, code snippets and tools for use with MySQL.
Planet MySQL is an aggregate of MySQL-related blogs, including Giuseppe's and mine -- http://planet.mysql.com
The website for the 2009 MySQL User Conference and Expo is at http://mysqlconf.com. MySQL Camp is a free conference at the same time as the User Conference. The details, including the schedule, are at
A collection of User Group videos is at http://technocation.org/category/areas/user-group. All the videos, including User Group ones, are
At the March 2009 Boston MySQL User Group meeting, Jacob Nikom of MITs Lincoln Laboratory presented Optimizing Concurrent Storage and Retrieval Operations for Real-Time Surveillance Applications. In the middle of the talk, Jacob said he sometimes calls what he did in this application as real-time data warehousing, which was so accurate I decided to give that title to this blog post.
The slides can be downloaded in PDF format (1.3 Mb) at http://www.technocation.org/files/doc/Concurrent_database_performance_02.pdf.
This talk discussed how to do real-time retrieval operations while doing concurrent high volume insertion, including:
* How to keep up with 1.5 Mb/second per server incoming data stream
* server hardware comparison between a multi-core AMD Opteron and a multi core Intel Xeon
* MySQL/Postgres comparison
* schema design
* design of the storage/retrieval benchmark