fashionwintersale15 Öle & Betriebsstoffe für Ihr Auto Kinderweihnachtswelt studentsignup Prime Photos boseFly Learn More Movember HI_SMART_HOME Hier klicken Shop Kindle Shop Kindle PrimeMusic


2,0 von 5 Sternen1
2,0 von 5 Sternen
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Stern
Format: TaschenbuchÄndern
Preis:46,85 €+ Kostenfreie Lieferung mit Amazon Prime

Ihre Bewertung(Löschen)Ihre Bewertung
Sagen Sie Ihre Meinung zu diesem Artikel

Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.

am 22. Januar 2012
This book was a disappointment. It should be called "MySQL Replication for System Administrator beginners":

- It shows in great length how to use netstat, a disk usage analyzer, or the Mac OS X Activity Monitor.
- There is a pointless story about some Joel guy (and how he becomes friends with a girl called Amy) throughout the book which just increases page count.
- A whole chapter deals with the very basics of database performance (read MySQL High Performance, if you want to know about that).
- Several pages cover two python scripts that essentially call an external command with a filename including a date. This can be done with a single line of bash by anyone seriously in the business.
- It explains how file globbing can lead to a wrong sequence in filenames,
- Bad editing shows in several repeated paragraphs.

The authors just don't seem to have a feeling about how to treat their audience by going to such low levels at times that it is close to insulting.

There are some nice parts of the book, though. The appendix with Replication Tips and Tricks finally shows that some author had indeed to deal with problems that happen in daily life.

I would have expected the book to delve into real world problems such as:
- schema changes with no or little outage
- table repairing best practises (i.e. quick recovery, decision making on whether to go to a backup, etc.) and going into reasons on why tables can get corrupted and how to avoid it
- high availability without replication. Sometimes it is not feasible to have multiple servers for certain tasks. How can you decrease downtimes in case something does go wrong?

Too bad, it could have been an interesting book, but it misses out on that chance.
0KommentarWar diese Rezension für Sie hilfreich?JaNeinMissbrauch melden