MySQL 8 Administrator's Guide

I like the book and will likely purchase their advanced Mysql 8 book. I hope they have improved editing in it.They need to have a human edit the text. There are many grammatical errors in the text. The missing articles, loose for lose, than for then, and many other such items are distracting. In the worst case these errors obscure the meaning of the text. I am not a grammar expert but this carelessness is a problem.

I was unable to give a rating of zero stars, which is why there is one star.Pros:-Almost no screenshots or diagrams that pad out the length of the book.-The diagrams that are printed are legible (very rare in technical books.)Cons:Where to start?- The typeface used is so large I wondered if I had bought a large-print version of the book for seniors. And there is a huge amount of white space also. This artificially enlarges the book length and makes it appear more comprehensive than it is. Using normal type face sizes and normal white spacing would reduce the page count by half. I look at page count when buying a book to judge the depth of information presented. Fooled me.- The amount of useful information presented is abysmally deficient. A closer inspection of the TOC should have clued me in when I see so many of the chapter sections are only 1 or 2 pages apart, or less. The section "Overview of the INNODB Storage Engine" is all of 3 sentences. Each one spaced apart as a separate paragraph. There are many, many sections treated the same way, with a just a few sentences under a huge section title.- As another reviewer noted, it is not possible that a native English-speaking person was used to proofread or edit this book. There are grammatical errors on almost every page I have read so far. And many of them are such that they make it very unclear what the intent is. Its like they released the draft as if it were a finished book. Not even a draft, more like an "alpha" draft. The sad aspect is that poor writing like this has become so prevalent that most people don't think it's a big deal.- There are out-right errors in the book. In the section "An Overview on Indexing" (Not "An Overview of Indexing"), the authors state: "As we know, the Primary key represents the column, or set of columns, which is most widely used for fetching records from the table". This is absolutely incorrect. Its completely unacceptable, not to mention embarrassing, that four supposedly proficient authors don't even know the definition of a Primary key in a relational database system.It was at this point that I threw the book in the trash.Addendum: I just noticed that one of the authors, Chintan Mehta, gave his own book a 5 star review. How lame is that?Addendum 2: Having been tasked with upgrading my employer's MySQL instance from 5.7 to 8, just for grins, I dug the book out of the trash to see what it proposed as an upgrade process. There were two (!) entire pages devoted to this critical (from an administrators point of view) process. Actually more like 1 and 3/4 pages. This is just sad.

There are no enough explanation. It seems is just copy MySql manual

Excellent book. Book explaining the advanced concepts in a very easy way, best thing in this book is you can cover the whole book within 1 week and every page will give you a fresh knowledge.There are exercises in each chapter to make sure you are learning the topics. This review can be helpful for others to take this book.Highly recommended.

I have't read the book yet, but the book came in pieces, literally it fell apart when I opened the package. I think this rating is appropriate considering that I have paid 39.99 for it.

It was $19 few days back, suddenly the price went up, very disappointing.

I liked this because it is easy to find what I want to know quickly, gets to the point! Not for the novice but it fills my need perfectly.

Excelente Livro

I had high hopes for this book.Over the past 30 years I have been a DBA for various databases (Oracle,DB2/UDB,SQL Server etc). Whenever I start learning about administering a new database, the first things I want to know how to do are : a) get a good backup b) work out the various restore scenarios, c) how do I deal with performance issues (so perform traces, evaluate and in the optimiser strategy and d) useful database parameters and how to manage them and come up with sensible valuesThis book covers almost zero about being able to secure (backup) your data, and next to nothing about restore. This in my view is a dreadful shortcoming.I don't know what the experience of the authors are, but it seems to me to be that this is merely a distillation of the help information, with little added in the way of real world experience. That's not what I buy a book for - I want to acquire some of the authors experience that is not in the help files.It is not an excuse that mySQL 8 is quite new, because most of the concepts have already been in place in 5.x for many years.So, sadly, I am very disappointed in the book.

Very poorly written book. Nothing described in detail. This book is not good if you want to refer for knowledge. Many places contents are wrong and clearly visible that either book is published in hurry or without a review. For me it is a no no. Going to return it.

All good!