Head First SQL

Anita Kuno writes "On a Sunday, a fellow user-group member suggested I learn SQL. The next day, an opportunity to review Head First SQL arrived in my email. Who was I to question? Prior to opening the couriered package, I had no knowledge of SQL, I knew databases were important, and I had seen the Head First website once or twice. Now, I can design and create databases, use mySQL databases, and understand questions and accompanying code posted to forums. The credit goes to Head First SQL's style, which introduces small bits of information, supported through multiple channels (such as photos with humorous dialogue, stick-men and stick-women, and input from critical personalities whose photos and input pop up throughout the book) regular tests and exercises so the new bit of data can find a home and settle into your memory. The regularly tested pieces of information are now in my brain so I don't have to look up the basic stuff." Read below for the rest of Anita's review.

Head First SQL is about RDBMS (databases) specifically mySQL (version 5.0 or newer) and includes features of other databases. The book defines a database, demonstrates how to navigate an existing database, and teaches how to create simple and complex databases, as well as how to let a database grow from simple to complex.

Foundational understanding of database construction and navigation is the focus. The target audience is those brand-new to the topic as well as those with an acquaintance with the subject and the need for a greater conceptual understanding of databases.

It focuses on the basics of databases, so the main information should remain pertinent until RMDBS get re-conceived. I think revisions, such as the reprint due out in December, will add to the strength of the book as typos and coding errors will be addressed.

The title accurately describes the contents and the subtitle "A Brain-Friendly Guide" describes the goal of the approach. The only requirements for working with the material are: a computer or access to one, the ability to identify your operating system, familiarity with downloading from the internet (links and instructions are provided in the book and the program mySQL community release is free (download instructions are given for Mac and Windows users, I believe that instructions for Linux are not included with the assumption Linux users can access the mySQL community release page and download the program without a play-by-play)), and the courage to learn a command line window user interface if you don't already know this.

Head First SQL is most useful to those who, like myself, have heard passing references to databases and other than knowing they are important have no grasp of what it is, means, or can do. Also, this will be a helpful tool for those who have some of the verbiage, enough to pass at a cocktail party, but who would feel the cold chill of horror if expected to design, construct, and implement a database in conjunction with any of their paid responsibilities.

This is the first book that I have read on the subject of databases and the first computer book that I have been able to finish. So much of the educational information about program x, language y, or application z, depends on a working knowledge of the other two variables. This is a great book for beginners. It talks about data types, it explains null, and then has null explain himself. It tells me the importance of the semicolon at the end. All basic stuff. All stuff that other books take for granted. Many times when I believed I wasn't absorbing anything, along came questions I could answer, a crossword I could complete and match-column-A-with-column-B exercises that demonstrated that I was actually learning much more than than I was giving myself credit for.

It includes illustrations, photos, clean layout, and bite sized pieces of information. All this comes from the goal of allowing both sides of the brain access to the information. It's exactly the kind of approach that I need to reinforce the terms and concepts as well as provide encouraging feedback to keep me progressing through the material. I'm also grateful that it entertains me and keeps me going back to finish the whole thing long after the first blush of excitement has worn away.

Links, to the mySQL program necessary to work with the material, are included in the book as well as a few other links in the appendices. The Head First website is a must in order to link to the forums, newsletter, blog and downloadable files to create various tables used in the book. Head First came out with a web app called Hands On SQL which I would encourage you to try. It won't work with all of the book's material but it is a good-looking tool.

You are welcome to read my submissions on the Head First SQL forum. My user name is anita. Also, the reprint that I mentioned above is due to be in stock as of December 3rd. I'm told by O'Reilly that it includes corrections for errata submitted thus far. Take a look at the Head First SQL homepage to download a sample chapter.

You can purchase Head First SQL from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Strange

[a_n_d_e_r_s (136412)]

why does this reads so much like an add for the book ?

Re:

[by Anonymous Coward]

why does this reads so much like an add for the book ?

I don't think I've ever seen a harsh review here on Slashdot. Perhaps the editors are of the opinion that a book need not be mentioned unless the reviewer thinks it's good, and since the has already been established to be good, the reviewer can go all out with hyperbole in praising it. If you want to see more critical opinions on a book reviewed here, check out the Amazon listing [amazon.com], where among the bogus reviews that often appear immediately for tech bo

No, THIS is an ad for the book:

[spun (1352)]

Head First! Apply directly to the SQL!

Head First! Apply directly to the SQL!

HEAD FIRST! APPLY DIRECTLY TO THE SQL!

Okay, I didn't say it was a good ad for the book...

Re:Strange

[mysqlrocks (783488)]

I'd stick with O'reilly or some publisher that focuses on computers personally.

The Head First [oreilly.com] series is published by O'Reilly. I think it's a great series of books - even for advanced users.

Re:Strange

[CodeBuster (516420)]

You beat me to the post by by a couple of minutes. I agree that even advanced users can get good stuff out of the Head First books, but it is important to remember that the bad jokes, stock characters, and corny vignettes presented in the books are not there as part of some misguided attempt to be cute, but rather as a research proven cognitive aid for helping us, the readers, absorb the most information possible into our brains in the least amount of time with the minimum amount of re-reading, backtracking, and resorts to external commentaries.

Note for GP: Understand what you are buying when you pick up a Head First book and why or else the wealth of useful information which they contain will be lost upon you simply because you cannot get past a pre-conceived notion about the presentation.

Re:

[aztracker1 (702135)]

Personally, I've been recommending the Head First HTML book for those starting out with X/HTML, simply because it is probably the best book for beginners I've seen... Not great for those who are already knowledgeable and able to hand-code HTML though. I have honestly been looking for a similar book to recommend for those looking into Javascript more... I like the JS Bible, but it's a bit cumbersome at this point, and should probably be broken down a little... Most of the O'Reily books are not best for inst

Re:

[CodeBuster (516420)]

I'd stick with O'reilly or some publisher that focuses on computers personally.

Actually, Head First Labs, the label under which the Head First series is published, is a subsidiary of O'Reilly Media Inc so the Head First series is published by O'Reilly.

who benifits?

[techpawn (969834)]

This sounds like a good intro book but nothing of use to a seasoned DBA. It reads as though you gain basic knowledge of the subject of SQL and some basic mySQL syntax but the day-to-day operations of a database are probably not covered since those are very version specific and generally done with odd T-SQL statements or GUI interface.

It sounds like a learn SQL in 24 hours book more than a SQL cookbook type resource, may be good for a developer who is starting out in the relational database world but I don't think DBAs will get much. At least, not from what the reviewer says.

Re:

[AlXtreme (223728)]

It sounds like a learn SQL in 24 hours book more than a SQL cookbook type resource

What would you expect from a book called "Head First SQL"?

And a minor nitpick: a seasoned DBA should know it is MySQL, not mySQL. That will be all.

Re:

[by Anonymous Coward]

No, a seasoned DBA should have forgotten as much as possible of MySQL and moved on to Postgresql or some other *R*DBMS.

Re:

[moro_666 (414422)]

Proper DBAs will just get a major headache from people who read a book and screw up their db servers thinking that now they have "god mode" on.

People, unless you have more experience with databases than "my little php page with mysql", don't touch "real" databases. You will go in with a grand idea that was avoided before by real DBAs that knew where locks, indexes, replications, transactions. backups and failovers matter. Newbies come in, create a shiny little script that makes the rest of server c

Re:

[YrWrstNtmr (564987)]

This sounds like a good intro book but nothing of use to a seasoned DBA.

And a book good for a seasoned DBA will be way over the head of a newbie. Not everyone is at the same level. Not every book should be written for 'everyone'.

Having said that...reading one book in a couple of days does not a SQL developer make.

I noticed the lack of theory in the ToC

[einhverfr (238914)]

Basically, it covers some basics of normalization, but no real background about the concepts or RDBMS's. IMO, one needs to cover, at very least, the fundamental concepts of relational math, and the mathematical definitions of SVD, FD's, MVD's, and the normal forms. Otherwise the book is actually teaching people to use RDBMS's wrong (MySQL is great at doing this too, so it is no surprise).

Re:I noticed the lack of theory in the ToC

[einhverfr (238914)]

IMO that sort of thinking is a mistake. It actually comes from the desire to cut down on planning time because management sees it as dead weight. And worse, people designing databases who have no clue what they are doing mathematically speaking.

In general, I have found that every hour of planning time spent tends to eliminate up to 10 hours of coding, and often as much as 100 hours of pre- and post-release re-engineering and bug fixing.

The goal ought to be to optimize time and expenses across the entire software lifecycle rather than cutting down on the most important places where time gets spent (on the design). This generally means spending more time on design, less on buzzword-compliance, and less on actual coding. If you do it right, testing and debugging effort go *down* as well.

Instead people end up with bloated monstrosities when better-designed products could have been built with less time an money.

Re:

[dHagger (1192545)]

My experience with the "Head First" series of books (I have read a few, not this one however) is that they are very good beginners books. Easy to read and easy to grasp the basic concepts of the subject they cover. Without loosing interest after a few pages (which in my experience is way too common with other books). And once you know the basics, you can go on and explore more advanced topics somewhere else.

On the other hand, once you know something about the subject, they are, well... not that good. You

Don't get in over your head...

[Vellmont (569020)]

On a Sunday, a fellow user-group member suggested I learn SQL...

Now, I can design and create databases


Database design and creation isn't something you pick up over 3 days. Sure, you can make something that works very quickly, but that doesn't mean it's a good design and isn't flawed. Designing a good database structure takes experience with the tradeoffs between full normalazation and added complexity, forseeing future needs, etc.

Re:Don't get in over your head...

[techpawn (969834)]

IMHO Creating a database is one thing, Designing is another entirely!

Making DDL scripts to run in the database is easy once you learn the syntax. Knowing their interaction with each other using Foreign keys, Indexes, and planning their future growth is a completely different set of skills that's only gained with experience with your data.

Re:Don't get in over your head...

[magarity (164372)]

Database design and creation isn't something you pick up over 3 days
 
Dude, it's FAR more terrifying than that. From the forums on that site:
 
anita Joined: 07 Oct 2007
Posts: 23
Posted: Sun Nov 04, 2007 1:30 am
Post subject: CREATE a TABLE with a FOREIGN KEY
I never noticed until this evening while building a database for a customer to use with her business, but I can't seem to find the place in the book where the code for creating multiple tables from two foreign keys exists
 
WTF: from 'I don't know anything about databases' to 'building a database for a customer' what amount of time? We don't know when "sunday" was, but even so it seems rather abrupt given that 'anita' has only joined the forum in October and is now designing databases for (presumably) paying customers. This HOWTO book must kick serious ass.

Re:Don't get in over your head...

[Tim Browse (9263)]

WTF: from 'I don't know anything about databases' to 'building a database for a customer' what amount of time?

Well, she did say:

"On a Sunday, a fellow user-group member suggested I learn SQL [...]"

Maybe it went like this:

I never noticed until this evening while building a database for a customer to use with her business, but I can't seem to find the place in the book where the code for creating multiple tables from two foreign keys exists

FFS, learn SQL!

Just a guess. :-)

Re:Don't get in over your head...

[magarity (164372)]

Re:Don't get in over your head... (Score:3, Funny)
 
It's not 'funny' dammit! It's 'customer getting taken for a ride'. The question is generated because she's using a joining table to solve a many to many between her customer and address tables and has named the constraints herself the same on each table instead of letting the system generate them. But WTF?? Address record goes to ONE customer record! If some other customer registers the same address just duplicate the %$#@ing 200 bytes of text but don't m-m it with the customer table!
 
Frack! Now I'm going to have to follow adventures of Anita The HOWTO Book Data Architect on that forum in the way one can't help but watch a train wreck in progress.

I would add

[einhverfr (238914)]

So far, I have almost always found heavily normalized designs are almost always a technical win when looking at future needs etc.

Note I am talking about normalization as a mathematical process based on data domains, functional dependencies, etc. This means building a database which is mathematically and semantically solid rather than working on program requirements (i.e. the structure of the data in the db should *not* be based on the program's data structures but rather on the inherent internal structure

Re:

[tuomoks (246421)]

Very insightful. IMHO this is the problem today, learn a little of one product dialect and you are the master of information management, yeah, great! Vellmont is absolutely right, database design is much more and corporate information management in those databases is even more. Even if a good start can be found in books it needs years, most often very specific industry knowledge and every day learning before you can master it. SQL dialects, structures, tables, even normalization are easy but really the futu

Re:

[Tablizer (95088)]

Database design and creation isn't something you pick up over 3 days. Sure, you can make something that works very quickly, but that doesn't mean it's a good design and isn't flawed. Designing a good database structure takes experience...

Agreed. Some of my best DB knowledge comes about from observing what didn't work, especially as changes were accumulated over the years.

Even something as simple as an Address table (or Contact table) can have gajillion different ways to do it, and gajillion different ways

Re:

[einhverfr (238914)]

Where the trick comes in is designing the database so that the types of queries you will be running against it take the least time.

There are times and places where you need to create a means to "run this specific query really fast" and in that case, good relational design is not a major issue. Nothing runs faster than a sequential scan over a summary table containing the exact results you want to obtain.

However, when you do this, you prejudice all other queries. Many queries may take far longer to run, or may not be possible at all.

IMO, good, highly normalized database design is a prerequisite for good long-term performance (unless

Hmmmm...

[by Anonymous Coward]

"This is the first book that I have read on the subject of databases and the first computer book that I have been able to finish."

Sounds like your aversage Slashdotter, doesn't it?

I have a question

[stoolpigeon (454276)]

How does one go about just getting technical books mailed to their home for review?

Yeah

[geekoid (135745)]

another person that learned database work from a book. Just what we needed.

Re:

[yakumo.unr (833476)]

The RIGHT book('s) would be fine, but they should be preaching normalization right from the get go to make damn sure the reader covers it, and is at least aware that if they don't normalize their data they will absolutely suffer. (yes sometimes you need weigh things up as another poster has mentioned, but that's part of it, and you damn well have to know about it in depth to make those judgements effectively)

This review doesn't so much as mention normalization once, so the only conclusion can be the book i

Re:

[iluvcapra (782887)]

I'm about to google it, but what's database normalization?

Re:

[yakumo.unr (833476)]

Database Normalization [wikipedia.org]

Re:

[afidel (530433)]

Yeah that was my thought too. Just enough knowledge to be really dangerous. Instead of using the enterprise servers costing tons of $ and maintained by highly paid, very knowledgeable professionals you get someone who's an amature that wastes tons of not quite as valuable time doing it themselves. And in the end the database(s) created by the amatures end up needing to be unraveled by highly paid developers and the same DBA's that should have handled it in the first place at the cost of many times what it w

Well, you have to start somewhere

[einhverfr (238914)]

We learn by doing but we can't do unless we understand the syntax.

Additionally, I would highly recommend Codd's Papers, and CJ Date's books on the subject. These will help to provide a theoretical framework for understanding what an RDBMS is all about.

Re:

[DragonWriter (970822)]

And I'm going to go out on a limb and guess that this fascinating book doesn't even begin to mention things like ER diagrams, or relational algebra.

But should it? I mean, sure, a database designer, administrator, or developer ought to know about relational database theory, design methodologies, normalization, etc. But is it necessary for a book on SQL to cover all that?

The best book on database design (in terms of covering lots of ground effectively and succinctly) I've seen doesn't cover much SQL (only eno

overnight experts, sigh

[magarity (164372)]

Prior to opening the couriered package, I had no knowledge of SQL ... Now, I can design and create databases
 
As a database designer/developer who occasionally does DBA duties as well I initially found this quote terrifying in the extreme. But as long as this experimenting about is done on your own PC for at least the next few months, it's great that you're getting a start on a new (to you) class of software tools. Way too many people plough on using spreadsheets where they should be using at least Access. I encourage anyone with accountant or small business owning friends to pass on this review.

Re:

[LurkerXXX (667952)]

Basically she's just saying she's another regular MySQL user. That's already terrified me for a long time.

Re:

[jayp00001 (267507)]

Can we get an AMEN here? How many of us have seen these ridiculously complicated spreadsheets users are sharing across the network that should be some flavor of database instead.

Couldn't finish the review...

[MilSF1 (710927)]

[pedantic mode: on]
Had a hard time with the blurb for that matter. if you are going to mention the name of a product several times, please learn how it's written!

MySQL
Not mySQL. For that matter, not mySQL, MYSQL, MY-SQL, or mSQL (that's another program actually)

It's all over their website [mysql.com]. Something that simple will help keep you from sounding amateurish as a reviewer.
[pedantic mode: off]

Normalization? Keys?

[Foofoobar (318279)]

Databases are a bit more than just queries. I find that most people new to databases start screwing up because thy don't understand that everything can't be stored as a varchar or that it's amazingly stupid to have every column in a table set as a key. Normalization is another big thing to knock into newbie database developer brains as well as naming conventions.

Personally, I stand by 'Database Systems' by Connolly and Begg. Not simple, not for newbies but it coveres everything you need to know including doing ER diagrams for your structure... something every DB admin needs to do more of.

Re:

[ErikZ (55491)]

I can see how some of those other problems could happen...but not normalizing?

Normalization is as integral to databases as SQL. If you're not normalizing your databases, you might as well not have them.

You've not done real database work

[tttonyyy (726776)]

...until your carefully crafted union of two huge tables fails, taking down a mysql server common to over 400 sites and incurring the wrath of your previously friendly hosting company.

Mental note - test locally first.

Re:

[afidel (530433)]

If you were doing real database work on a well run DB you wouldn't have been able to take the DB down =) Real DB's have resource limiters that allow the DBA to insure that no one user can exhaust resources to the point of taking the DB down. We even limit the percentage of system resources a user can take just to make sure that one bad report doesn't slow down OLTP processing. I'm not the DBA but I know enough to know that there are toys and then there are real business tools.

Re:

[tttonyyy (726776)]

If you were doing real database work on a well run DB you wouldn't have been able to take the DB down =) Real DB's have resource limiters that allow the DBA to insure that no one user can exhaust resources to the point of taking the DB down. We even limit the percentage of system resources a user can take just to make sure that one bad report doesn't slow down OLTP processing. I'm not the DBA but I know enough to know that there are toys and then there are real business tools.

Indeed. This was a mysql database that I had previously tested long queries on. I was monitoring the progress of the query when the server went unresponsive. All hell broke out from there.

Not the most imformative review

[ChrisA90278 (905188)]

I wonder if this book covers what's really importent. How to design systems that use databases. I've seen way to many system designs where the DBMS is grossly abused. For example to self-educated programer did not know about "joins" so he searches one table, holds the value in a variable andthen looks it up in a related table. Of corce he also does not think about locks, deadlocaks and transactions. You be surprized to see how common this is. I've seen tables design be people who must have never read

Perfect for a certain group

[Hashi Lebwohl (997157)]

I'm reading a lot of negative comments about this book, maybe that's to be expected due to the technical nature of /. readership.

However, as a DBA and DB dev myself, I know one person that I am personally going to buy this book for, maybe as a Christmas present.

My boss, of course! I spend hours per week trying to explain to him why I do things certain ways. This is because he has a slight technical background in SAP, and has just enough knowledge to be dangerous. I would love for him to read this book, i

Please include reviewer's background

[GreggBert (89663)]

It would be helpful to include your own background when doing a review. While I know not everyone works with SQL every day, it might help to put the review into context if we knew what level of technical or development experience the reviewer had. It would make it easier to possibly recommend the book to others if we knew what background the reviewer had in relation to those we might possibly recommend the book to.

Re:

[Apiakun (589521)]

Thank you for providing me with the first laugh of the day!

Re:

[Critical Facilities (850111)]

Maybe the same guy who left out the H in apostrophe? Just pointing out the irony ;-)

Re:

[einhverfr (238914)]

The problem is that relational databases are built around a very specific mathematical model. If you don't understand the principles of RDBMS's and at least have a basic clue about the math behind them, you will never be able to use them effectively.

Most of the time, a lot of us end up having to clean up databases designed by programmers. A lot of the time, the programmers don't really grasp the problems inherent in ignoring the O-R Impedance Mismatch issues and so we have a lot of horrid databases out th

Re:

[Random BedHead Ed (602081)]

Whats wrong with using apostrophe's?

Re:

[DragonWriter (970822)]

These books are not "The in depth" kind of books nore are they any good as reference literature. But stil they push the information through in an humorous way. Meaning you learn not knowing that you are learning!

If I'm going to shell out money for a book to learn something, why would I object to knowing that I'm learning?

And, if I'm going to shell out money for a book to learn something, why would I not prefer something that is either in depth, useful for reference, or both, especially given that the Head F