High Performance MySQL: Optimization, Backups, Replication, and More,   ISBN:9780596101718

Customer Rating: 

How come I did not comment on this book before? Its been some time since I got it, read it, and used it! That's what this book is... useful, very useful. We had to optimize a DB, specially a huge table with millions of numbers and managed to go from tens of seconds to milisecs. I would say it was.. well, very useful;)

Customer Rating: 

A good book for developers that want more. They want to optimize their scripts and really understand how MYSQL works also behind the scene.

A must have book

Customer Rating: 

For weeks, I'd been searching online, trying to find out what MySQL's slow queries log actually was. Eventually I found it.

And then I got this book, and there was an even better description than what I'd found in MySQL's online documentation.

I swear, after I've worked my way through this book, if I don't double my wages, I'll be a monkey's uncle.

Customer Rating: 

This book helped me understand how MySQL works internally and a lot of tricks to improve the performances of both the server itself and the SQL queries I run against it.
If you want to improve the performances of MySQL related work in your applications, this book is definitively for you

Customer Rating: 

I bought this book hoping to get a detailed understanding of how to best create and use indexes for my high traffic web site. While the book does a great job of covering the pros and cons of standard indexes, it devotes only a single page to the utility of index_merge (introduced in Mysql 5.0). Combined with a general dearth of information about index_merge on the web, this was a really disappointment, since index_merge seems to afford the possibility of using multiple, smaller indexes, rather than smaller number of bulky indexes (as this book recommends).

In my eyes, a thorough analysis of indexing techniques in Mysql 5+ must discuss the strategic opportunities afforded by index_merge. It would seem to me that this gives the developer the ability to simply index the fields they want indexed, without having to sweat left-precedence of combined indexes or trying to make long indexes that include all of the possibly needed indexes in an order that will satisfy all possible query combinations.

If limitations to the utility of index_merge make some of these possibilities not feasible, the book ought to at least give a rundown of the pros and cons of index_merge vs. compound indexes.

The near-total omission of a new feature that could have profound implications upon the most optimal way to query & index makes me recommend this book with a tablespoon of salt.