SQL (Structured Query Language) is a standardized query language for requesting information from a database. Historically, SQL has been the choice for database management systems running on minicomputers and mainframes. Increasingly, however, SQL is being adapted to PC database systems because it supports distributed databases--databases that are spread out over several computer systems, so that several users on a local-area network can access the same database simultaneously. Although there are different dialects of SQL, it is the closest thing to a standard query language that currently exists. SQL in a Nutshell is a practical and useful command reference to the latest release of the Structured Query Language (SQL99), helping readers learn how their favorite database product supports any standard SQL command. This book presents each of the SQL commands and describes its use in both commercial (Microsoft SQL Server 2000 and Oracle 8i) and open source (MySQL, PostgreSQL 7.0) implementations. Each command reference includes the command syntax (by vendor, if the syntax differs across implementations), a description, and informative examples that illustrate important concepts and uses. SQL in a Nutshell is more than a convenient reference guide for experienced SQL programmers, analysts, and database administrators. It's also a great learning resource for novice and auxiliary SQL users such as system administrators, users of packaged client/server products, and consultants who need to be familiar with the various SQL dialects across many platforms.

Rating:

Rating:

Rating:

SQL in a Nutshell Review,  July 18 2001
Submitted by Brian Lalonde   [Respond | View]



This is a decent first edition, but I would like to see some additional info about desktop databases. Occasionally, DBAs (for whatever reason) get forced into using FoxPro, dBase, Access, FileMaker, etc.

A comprehensive reference that contrasts the syntax and datatypes of those databases with more familiar ("real") database systems could dramatically cut down on trial-and-error time. Knowing, for example, that Access uses "autonumber" fields, rather than SQL Server's "identity" would be useful to someone who does not have access to Access, but is creating their schema through an Access ODBC driver.

Even a simple appendix showing what ODBC drivers (or levels) support would help seasoned SQL programmers leverage their experience into other markets.




SQL in a Nutshell Review,  May 27 2001
Submitted by Miles Elam   [Respond | View]

The book covers a topic (like creating tables) in the general (SQL99) and then in the specific (by database). This would make the book an excellent resource if implemented well. Unfortunately the actual result is a disjointed and inconsistent treatment of the variations between databases. Even worse, when a subsection specifically named for a particular database comes up, examples for other databases get sprinkled in the mix.

It ended up being very difficult to find the exact syntax needed for the database I was using. I started to copy/modify an example only to find that it was a MySQL example right smack in the middle of a section named for PostgreSQL. At the very least, a new subsection header called "examples" would help tremendously.

While I was turned on to a few concepts of which I was previously unaware due to my lack of familiarity with a wide variety of database products, I still ended up just sifting through the online documentation of the database I was working on and printing out the syntax-related highlights. This was precisely what I was trying to avoid when I bought the "Nutshell" book.

As a final gripe, while the back cover states that the book covers PostgreSQL 7.0, the first chapter goes on to state that the reviewed version of PostgreSQL is 6.5. I bought the book based upon the table of contents, the description on the back cover, and the good name of O'reilly. I was sorely disappointed with my investment.

I look forward to a (much needed) second edition that demonstrates a great deal more care. A good cross-implementation reference is a much needed resource, but this effort does little to solve that.




SQL in a Nutshell Review,  February 02 2001
Submitted by Peter Dobratz   [Respond | View]

Recently, I have started working on a project which requires knowledge of SQL. We were originally planning to use an Oracle database, but switched to postgreSQL. This book has a concise introduction to relational database theory, then provides syntax for all SQL commands along with variations from 4 vendors. If the pattern continues, we may end up switching database vendors again in the future, so we are trying to write SQL that works on as many databases as possible. This book provides the necessary information to do so. I would not want to work on a project involving SQL again without it.


SQL in a Nutshell Review,  January 29 2001
Submitted by Allie Rogers, Jr.   [Respond | View]

Not O'Reilly's best effort.

There is little meat to the descriptions of the vendor-specific SQL variants. Specially, I expected to see details on the differences between Sybase/Microsoft data types, functions and their Oracle counterparts. Or how PostgreSQL and MySQL syntax differ. Sure, there are tables and tables of syntax, but no context or descriptions of how each vendor implements the same type or function; how they are the same; how they are different. Since each vendor already provides a reasonable set of card-oriented, one-page documentation, this volume seems to fill no specific niche nor perform any really useful function, unlike most of the "Nutshell" books.

There are no tricks or tips to speak of. When they are mentioned, there are no specifics given for how or why.

Overall, this book was very disappointing, especially in light of the VERY STRONG effort put forward in "Transact SQL Programming" book by the same author and publisher. While that volume provides no specific information on MySQL or Oracle, neither does "SQL in a Nutshell". Further, "Transact SQL Programming" is just plain a better SQL book, overall.

See larger cover
Browse within this book