Hi David.

I never really had any problem with the MySQL engines themselves. If I stuck with myISAM I got single table backups and single table restores out of the box. Too cool for school, that.

My performance problems were all in the connector. Queries that ran, or crawled rather, in the application came back instantly when pasted into SQLYog. It's was a hot server on a clean network and all inside the four walls. The latest and greatest of all components too. I wish that I could share real world statistics with you but that is all tucked away in the project folders under the confidentiality blanket.

Then is have to look at what, IMHO, is the crippled way they implemented triggers, functions, and stored procedures. I can't wait for MySQL to "grow up" in this area. You can read that both ways. One, I'm hoping they do and anticipating the need for another look, and Two, I'm not waiting but moving forward without them. Sad really.

It turned out, for us, that the low cost of acquisition was not enough to overcome the issues.

MySQL is a great thing and will work well for many people. It has feature sets and attributes that can make it "killer" in lots of places.