Rating: 
Summary: DBAs and novices alike need this book
Review: This is an awesome book. DBA's need it for reference purposes. Novices need it to learn what the heck they are doing. But it is especially useful for those of us who work in companies that can't make up their minds which database we are going with, and so we have to move back and forth between several. I have worked with Oracle, Informix, Sybase, MySQL, and Microsoft's SQL Server all in the past 4 years. This is an excellent book. Everyone should have at least 1 copy.
Rating: 
Summary: Slimline but practical
Review: When I first saw this book I was perhaps a little doubtful it would be any good. It certainly is slimline when put on the shelf against my other O'Reilly Nutshell titles. I found it hard to believe that SQL in a Nutshell covers the SQL syntax of no less than 4 databases (Microsoft SQL Server, MySQL, Oracle and PostgreSQL), but when you actually see the way that it's been put together, it all makes perfect sense.Rather than having seperate sections for each of the SQL dielects, all statements and functions are listed together with any vendor specific information noted where needed. The main advantage of this style of organisation is that it helps you to identify any problems with portability between the databases you may be having. As can be expected with any Nutshell book, the history of SQL is discussed along with all the basic ideas and concepts that go with it. Even if you don't use one of the databases talked about in the the book, you are sure to be able to make good use of it as it makes frequent reference to the SQL standard.
Rating:
Summary: Maintaining several SQL implementations?
Review: [A review of the 2nd edition, 2004.]
Perhaps the best virtue of this book is that it spans all the major variants of SQL - db2, Oracle, MySQL, PostgreSQL and Microsoft's SQL Server. The authors are not beholden to any particular vendor. Thus the book describes the common ground. That is, the commands and usage that are most likely to be the same or similar across these implementations. Because a major use of this book might be in migrating. To this end, the more code you can have in this common area, the less painful the migration.
Another possible usage is if you are a DBA in charge of running 2 [or more] of these implementations. Perhaps due to some legacy issues, you have to support them. If you cannot merge SQL code into one common version, you can get problems. Being able to use this book to find quickly common commands and options to those commands might greatly help you maximise a common body of code.
| 
