Inside Microsoft® SQL Server® 2008: T-SQL Programming

Errata for Inside Microsoft® SQL Server® 2008: T-SQL Programming




The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page xxiv
Last paragraph

When I access the link for the 'Find Additional Content Online' website provided in the last paragraph my IE displays an error 'can not display' the page... I've copied the link for the website from the text. Please confirm if the website is still availible and that the address provided is correct.

Note from the Author or Editor:
Confirmed. This link does seem to be inactive. For resources related to the book best visit the book's companion website here (page is for both T-SQL Querying and T-SQL Programming): http://tsql.solidq.com/books/insidetsql2008/.

Anonymous  Jun 10, 2011 
Printed
Page vii
number 7 in ToC

Number 7 in ToC is printed as "Temporary Tablesand Table Variables", which should instead be "Temporary Tables and Table Variables".

Anonymous  Jun 22, 2011 
PDF
Page 117
First two Query form examples.

Printed as: You can indicate that specific parameters or variables should be assumed as unknown for optimization by using the following form: <query> OPTION(OPTIMIZER FOR(@p1 UNKNOWN, @p2 UNKNWON, ...); You can also indicate that all parameters and variables in the query should be assumed as unknown for optimization by using the following form: <query> OPTION(OPTIMIZER FOR UNKNWON); Should be: You can indicate that specific parameters or variables should be assumed as unknown for optimization by using the following form: <query> OPTION(OPTIMIZE FOR(@p1 UNKNOWN, @p2 UNKNWON, ...); You can also indicate that all parameters and variables in the query should be assumed as unknown for optimization by using the following form: <query> OPTION(OPTIMIZE FOR UNKNOWN); (Differences:- 1. 'OPTIMIZER' should be 'OPTIMIZE' in bohth query forms 2. Typo 'UNKNWON' in 2nd query form)

Note from the Author or Editor:
Confirmed. * Both references to "OPTIMIZER FOR" should be replaced with "OPTIMIZE FOR" * Reference to "UNKNWON" should be replaced with "UNKNOWN" Thanks for reporting this! Cheers, Itzik

Arkajeet Dasgupta  Feb 17, 2013 
Printed
Page 154

Sentence should be removed On page 154, in the last sentence of the fifth paragraph should be removed. Change: "For encapsulation purposes, I’ll create three stored procedures: one that sets the signal, one that clears it, and one that returns it. Eventually I didn't create them as special procedures." To: "For encapsulation purposes, I’ll create three stored procedures: one that sets the signal, one that clears it, and one that returns it." Microsoft Press is committed to providing informative and accurate books. All comments and corrections listed above are ready for inclusion in future printings of this book. If you have a later printing of this book, it may already contain most or all of the above corrections.

Microsoft Press  Jul 13, 2010 
Printed, PDF
Page 190
figure 4-15

There's a pointer to first 1:47120 that shouldn't be there.

Note from the Author or Editor:
Mistaken pointer should be removed.

AdamZ  Dec 19, 2011 
Printed
Page 226
First sentence below third code sample

Currently: What you end up getting in @rc is the number of rows affected by the first assignment (namely 0), instead of the number of rows affected by the suspect statement. Should be: What you end up getting in @rc is the number of rows affected by the first assignment (namely 1), instead of the number of rows affected by the suspect statement.

Anonymous  Oct 25, 2011