Book Review: Expert Consolidation in Oracle Da ...
Doug's Oracle Blog
Display comments as (Linear | Threaded)
It's fair to declare up front that the author of this book, Martin Bach, is one of my best friends in the Oracle community (even though I haven't known him for that long really) and someone who I truly respect for all sorts of reasons, both professionally and personally. One of the personality traits I think we share is that, if we thought something was truly awful, we might not call it out as such but we would certainly raise an eyebrow, chuckle internally and then have a private conversation later about just how awful it was!
So if this book was awful, I would probably just pretend that I hadn't read it and certainly wouldn't be writing about it! He *might* remain a friend but I might have to look for new friends who didn't write awful books (I wouldn't tell him that, of course!)
Fortunately, it is far from awful.
Although Martin has previously written great content on the second edition of the RAC book (in fact I think one of our earliest contacts was a quick informal review of the ASM chapter) this really reads like *his* book and his voice runs straight through the middle (and sides) of it, particularly in the the earlier chapters - 1, 3 and 4. Maybe I should actually talk about what I mean by that and what the book is like instead of sucking up to Martin for a moment?
- It reflects what is truly going on in the day-to-day world of Enterprise Database Computing. Which is to say that it reflects business realities of cost savings, increased consolidation and balancing technical possibilities with practical realities. This is important. I remember when I first started out in IT, I think I was technically good, understood computing subjects and could pick up new ones pretty quickly, helped by my prior career as an assembly language developer and yet I didn't have the first idea of what happened in the IT departments of the big companies because I'd never worked in one. It was very frustrating and took me a long time and a bit of luck to get the right job and learn it as I went. If you've never worked in a big bank, for example, Martin explains what is actually going on in those banks right now because he's been there, seen it and done it. (Or at least attempted to do it whilst fighting the usual internal bureaucracy!) If I'd had this book at the start of my career, I would have understood what banks were looking for and the language they were speaking!
- It's current. Although this won't remain true for some sections of the book (things change so fast in Oracle-land), the coverage of 12c is likely to ensure that in practical terms, it will be several years before even the majority of the technical material is out of date, regardless of what Oracle Corp might announce at the next Openworld conference! Enterprises do move forward constantly to maintain continued support (even when they have current versions that just work), but they don't tend to wrap themselves up in new versions of Oracle for a good couple of years.
- It's accomplished and knowledgable without being smug or arrogant. This is a really important part of any book for me and one that I rarely find in the right balance. I want to read books by those who truly know and understand the subject matter, so I'm likely to gravitate towards books written by experts, but the purpose of the book should be to educate me and not to show off the authors knowledge as some precious gift from a far-flung planet! I wrote about this many years ago and the mere tone of some technical books is enough to make me stop reading. Martin doesn't tell you things because he's clever and you're not. He tells you them to help you do your job and to make your life easier by not having to go through the same pains that he probably did at first. But that doesn't mean the book is fluffy and lightweight either!
- As most authors will tell you, the quality of any technical book is largely dependent on the technical reviewer(s) because it's very difficult to spot one's own mistakes at times and I think that any treatment of technical matters benefits from a second opinion. Frits Hoogland might also be a friend but I also know he has the eye for detail and commitment to technical accuracy a book like this demands. I don't think he had much work to do on the descriptive passages (I happen to recognise Martin's stellar command of the English language and style) but I bet he pulled him up on the odd mistake or two
As seems increasingly the way with anything I write purporting to be a book review, I don't seem to have mentioned much about what is in the book and what it will teach you, but I suppose it's not exactly difficult for you to check those things yourself. When someone writes a book that I enjoyed reading and found myself nodding my head to as much as this one, I think it's worth my time nudging people in the right direction but letting them decide for themselves if it's the right book for them. Recommended, though!
P.S. I should also point out that I have not worked through the examples in the book because I'm in the process of changing my home setup but, when I do, this is the book I'll be turning to as I work my way through 12c installations.
Part 1 - Default options - GLOBAL AND PARTITION
Part 2 - Estimated Global Stats
Part 3 - Stats Aggregation Problems I
Part 4 - Stats Aggregation Problems II
Part 5 - Minimal Stats Aggregation
Part 6a - COPY_TABLE_STATS - Intro
Part 6b - COPY_TABLE_STATS - Mistakes
Part 6c - COPY_TABLE_STATS - Bugs and Patches
Part 6d - COPY_TABLE_STATS - A Light-bulb Moment
Part 6e - COPY_TABLE_STATS - Bug 10268597
A couple of posts about Incremental Stats confusion