On page 25 you'll notice that in the second paragraph discussing Remote Data Objects, the text reads as:

"It was created by using a very thing wrapper around ODBC..."

This is of course a typo, and should actually read:

"It was created by using a very thin wrapper around ODBC..."

In short, we need to replace "thing" with "thin".

Last paragraph tells the reader that multiprotocol with respect to accessing SQL directly over the internet will be covered in the security chapter. This is not the case.

In the line above the figure on page 67, the text reads:

"Choose the Results in Grid option and re-run the previous query..."

The text here should actually read as:

"Choose the Results in Text option and re-run the previous query..."

In this paragraph, you may have noticed how the text reads as:

"In addition, SQL Server must go out and figure out..."

Of course, this should simply read as:

"In addition, SQL Server must go and figure out..."

You may have found yourself being left a little perplexed by the text here - should this be the case, we offer our sincerest apologies. In order to clarify, "customer name" in this paragraph should actually read "company name".

This modification also helps to address any confusion that may have arisen regarding the sentence in the paragraph below the screenshot on page 80, which starts:

"The other two columns are..."

On this page, you'll find a large table, illustrating the various ways in which operators can be used in conjuction with the WHERE clause. Each operator has an associated "Example Usage" and you'll notice that in some of these examples, any strings that are used, are contained within DOUBLE QUOTES, for example:

<Column1> LIKE "ROM%"

However, this is erroneous, and if you are experiencing problems here, this could well be the cause. You see, all strings that are to be used in a manner similar to this should actually be enclosed in SINGLE QUOTES, for example:

<Column1> LIKE 'ROM%'

Despite the claims about being unable to change the order of columns in a SQL Server 2000 table, you can reorder columns from the Enterprise Manager (EM) simply by dragging and dropping to any desired location in the table design view.

The self-referencing foreign key can be added to the table without using a 'primer' row by simply adding WITH NOCHECK to the ALTER TABLE command shown in the middle of the page. (also see the ALTER TABLE command in SQL Server Books Online.) This is much quicker and simpler than either creating a primer row or only doing this type of contraint on a nullable column.

On page 237, paragraph 1, the first sentence states:

"With the addition of our new column..."

When it should actually read as:

"With the addtion of our new table..."

In the first paragraph on page 276, in the sentences .......larger size cuts down on the number of page changes, which in turn cuts down the logical reads. Fewer logical reads usually means less time and effort spent in I/O, and better performance. the words logical reads should be physical reads. Fewer physical reads will indeed mean better performance.

On the first code snippet of page 328, you need to ensure that 'QUOTED_IDENTIFIER' is set to 'ON' with SET QUOTED IDENTIFIER ON

On page 340, in an example, the book used double quotaions for print command. It did not work and gave me errors and changed them to single quotations. Dong.

On page 457, on the second line of the COMMIT TRAN section, the text currently reads as:

"That is, the affect of the transaction..."

This should actually read as:

"That is, the effect of the transaction..."

Between pages 529 and 534, you may have noticed that UPDATED_COLUMNS and COLUMNS_UPDATED seem to be used and interchanged when referring to functions, without any explanation. This interchanging of function names is actually erroneous, and you should note that all instances of UPDATED_COLUMNS should be replaced with COLUMNS_UPDATED. Here are some more specific details as to where exactly this errata applies:

Page 529:

UPDATED_COLUMNS in the 2nd bullet point should read as COLUMNS_UPDATED.

Page 532:

The headings at top and further down the page are incorrect, and should in fact refer to COLUMNS_UPDATED. Also, the instance of UPDATED_COLUMNS in the text paragraph at the bottom of the page should be replaced with COLUMNS_UPDATED.

Thing being selected should read "CategoryID", not "CategoryI"

line 6
Thing being selected should read "CategoryID", not "Cate"

Second paragraph needs a correction to the font of a character.

The last line of the paragraph read:
"ensuring that our <code>id</code> and <code>idrefs</code> will be enforced."

The last line should read:
"ensuring that our <code>id</code> and <code>idref</code>s will be enforced."

Where <code> means the text is in Courier.

The second bullet should contain the word "xmltext" instead of "xmldata", as it currently stands.

Hence the final sentence should read as:

"If an attribute is provided with the xmltext directive..."

Rather than:

"If an attribute is provided with the xmldata directive..."

The bcp example at the top of the pages uses a comma as delimiter between the records. Bad idea, because the company names contain commata. An re-import would be nearly impossible.

In the second indented paragraph on page 882, the second sentence should have the word 'opinion' instead of the word 'option'. Therefore the sentence should read: 'Well, that's a garbage recommendation in my not so humble opinion...'

You may have noticed that in the index of this book, on page 1373, there is an index entry that states:

"Open Database Connectivity see ODBC"

In turn, you may then have found that the entry for ODBC is missing from the index. Introductory information regarding ODBC and other data access models are in fact discussed on pages 24 and 25. However, for a more detailed discussion of this subject, you may find the supplementary titles that are referred to on page 25 to be of particular interest.