As much as I’d like to be able to produce completely error free books, the reality of the computer publishing industry is that the pace at which books must be written and released makes this very difficult. And regretfully, my own books do have sporadic mistakes and typos scattered throughout them.
For the benefit of my readers, here is a current errata for Sams Teach Yourself SQL in 10 Minutes – Second Edition. Feel free to print this page for future reference.
And as always, if you come across errors that I do not know about, please let me know. I’ll make sure they are added to this list, and will try to have them corrected in future reprints.
Original printing (260 pages, published May 1, 2001)
| Page | Location | Correction |
|---|---|---|
| 8 | Last line, word “alphanumeric”. | Should be “alphabetical”. |
| 31 | Second INPUT block, first line. | Should read: “SELECT vend_id”. |
| 41 | The Percent (%) Wildcard | If using Microsoft Access, use * instead of %. |
| 43 | Both INPUT code listings. | Some databases (including Microsoft Access) pad fields with spaces, and so these two SELECT statements will not return data as the WHERE clauses will not match. The fix is to add a % at the end of the search pattern (before the second ‘). |
| 48 | Both OUTPUT blocks (and output on pages 50-52). | The downloadable sample Access files have NULL values for two of the rows in the Vendors table. When these values are used in a calculated value, some DBMS’ (including Access) will return a completely NULL value. As such, your OUTPUT may be missing two rows (for the two International addresses). One solution is to save an empty string in that column instead of a NULL value. |
| 59 | References to UPPER() function. | If using Microsoft Access use UCASE() instead. |
| 60 | Soundex() example. | This example may not work if using an Access database. If you receive an “undefined function” error message then you will not be able to use the soundex() function. |
| 61 | DATEPART() function used in INPUT listing. | If using Microsoft Access use ‘yyyy’ instead of yy. |
| 68 | Last word on page, “criteria”. | Should be “criterion”. |
| 72 | First line of first INPUT, word “items_orders”. | Should be “items_ordered”. |
| 81 | Analysis block, second to last line word, “three”. | Should be “four”. |
| 83 | Second INPUT listing, final line of code. | Should read: ORDER BY COUNT(*), order_num; |
| 129 | Note, last line: later | Should be: latter |
| 138 | Analysis block, second line, word “preceding”. | Should be “following”. |
| 140 | INPUT block, line beginning “vend_zip”. | There is a comma missing at the end of this line. |
| 153 | First INPUT, line beginning RTRIM. | There is a comma missing after the word “cust_address2”. |
| 153 | Second INPUT, line beginning RTRIM. | There is a comma missing after the word “cust_address2”. |
| 154 | First INPUT, line beginning RTRIM. | There is a comma missing after the word “cust_address2”. |
| 164 | Analysis block, fifth line, word “currenthighest”. | Should be “current highest”. |
| 182 | INPUT block, line beginning “vend_zip”. | There is a comma missing at the end of this line. |
| 183 | Last line of page. | Missing word ADD before the word CONSTRAINT. |
| 183 | Last line of page, word “REFERNCES”. | Should be “REFERENCES”. |
| 186 | Code in INPUT block. | Missing word ADD before word CONSTRAINT. |
| 198 | First bullet, third line. | “item_price” should be “prod_price”. |