PUBLIC MARKS from mbertier with tags mysql & clevermarks

Hiring a MySQL DBA can be challenging, especially when the demand for MySQL DBAs is greater than there are qualified people to fill those positions. This article will go into some details on how to recruit, recognize, and interview a great MySQL DBA. (For the rest of this article, MySQL DBA and DBA are the same.)

I have created a shortlist of what the Enterprise customers like to see with Proxy. Jan and the engineering team are working at some of these features, but it would be really great to see the contribution from the Community as well.

As I mentioned before, search was one of most interesting problems I worked on at Audiogalaxy. It was one of the core functions of the site, and somewhere between 50 to 70 million searches were performed every day. At peak times, the search engine needed to handle 1500-2000 searches every second against a MySQL database with about 200 million rows. It was frequently hard to design for more than 10 or 100x our current traffic (and our growth was so dramatic that there wasn’t really ever time to spend more than a few weeks on the problem), so it wasn’t until the 4th major iteration on the cluster design that I really considered the scale problems to be solved.

This page and related pages describe various issues surrounding the Web 2.0 tagging and folksonomy concepts, including discussions on schema architecture, common data access patterns, and replication/scale-out guidelines.

In this post I present my MySQL Swiss Army Knife, all the tools that make my life related to MySQL easier :-)

They don’t exist on the market today.

GreenSQL is an Open Source database firewall used to protect databases from SQL injection attacks. GreenSQL works in a proxy mode and has built in support for MySQL. The logic is based on evaluation of SQL commands using a risk scoring matrix as well as blocking known db administrative commands (DROP, CREATE, etc). GreenSQL is distributed under the GPL license

When IBM, Adobe, Oracle, Novell, SAP, or other proprietary companies release even a modicum of code, they get universal plaudits. When 100% open-source companies like Red Hat and MySQL rejig the way they release code (while still releasing it and fully complying with open-source licenses), they get tarred and feathered.

MySQL fundamentally misunderstands their community

DorsalSource is a community-focused website whose goal is to provide builds of MySQL and related products. It will be maintained and run by the community. Solid Information Technology and Proven Scaling took the initiative to launch it. We will add additional contributors over time.

I gave a tutorial at OSCON last week on tuning MySQL queries, the EXPLAIN statement, the optimizer, and benchmarking. I've gone ahead and put the tutorial materials online now:

talks about current state behavior and performance properties of Innodb, Falcon, PBXT and SolidDB Storage Engines

RAID is dying. Shocked? The prediction might be a bit early for some folks. It’s still somewhat conventional for some people to think that RAID is a conservative way to scale your IO.