“In many of the more relaxed civilizations on the Outer Eastern Rim of the Galaxy, the Hitchhiker’s Guide has already supplanted the great Encyclopaedia Galactica as the standard repository of all knowledge and wisdom, for though it has many omissions and contains much that is apocryphal, or at least wildly inaccurate, it scores over the older, more pedestrian work in two important respects. First, it is slightly cheaper; and secondly it has the words DON’T PANIC inscribed in large friendly letters on its cover.”
—The Hitchhiker’s Guide to the Galaxy by Douglas Adams
Next installment: A Long Time Ago
A couple of years ago, I came across the following honest admission on AskTom:
“After 15 years development, implementation and administration of Oracle Databases I’m going to be totally honest.
1. I have used Oracle 6-11g
2. I do understand the concepts of Oracle RDBMS databases
3. I do find PL/SQL ‘relatively easy’
4. I have been following Tom Kyte in web and print since the mid 90s from his comp.databases.oracle days
5. I’ve always been a proponent of modular well written and well documented code
6. I’ve always been a big believer in as simple and logical a common sense approach as possible
1. I still find SQL very difficult
2. I still can’t easily think in sets
3. I still can’t really read an EXPLAIN PLAN with more than a few lines of indentation
4. I think I have used ‘real’ analytics about 3 times – after seeing it done in a specific example on this site
5. I would still bet that the majority of SQL writers out there would have no idea about or concept of query execution plans”
The above comment motivated me to start collecting notes for a book on SQL which puts the query execution plan front and center. My plan is now to turn my notes into a series of blog posts with the goal of assembling them into a self-published book at some future date. Hop along for the ride and, above all, DON’T PANIC. You’ll soon be master of the EXPLAIN PLAN.
To be continued.
Copyright © 2014 Iggy Fernandez
Looking forward to reading your blog, and passing the information on to our developers. (smile). Stover