Errata
Errata for MCITP Self-Paced Training Kit (Exam 70-444): Optimizing and Maintaining a Database Administration Solution Using Microsoft® SQL Server™ 2005
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 xxvi |
Incorrect Service Pack listed for Windows Server 2003 in software requirements |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 107 |
The word "maximum" is used in place of "minimum" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 340 |
Missing backslash in server path name |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 445 |
bin data type referenced in place of bit |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 729 |
UNIQUE constraint referenced in place of DISTINCT |
Microsoft Press | Jul 13, 2010 | |
Other Digital Version | CD-ROM |
Incorrect explanation for practice test question answer In the practice test included on the Companion CD, one of the questions reads: "You are creating a database maintenance plan. Which of the following available maintenance tasks will compact a clustered index?" The third sentence of the answer explanation is incorrect. Change: "The Update Statistics task can be used to compact a clustered index." To: "The Update Statistics task cannot be used to compact a clustered index." |
Microsoft Press | May 06, 2010 | |
Printed | Page 7 |
Code sample is not valid SQL Server code On page 7, the code sample in the Real World box is for Oracle, not SQL Server. Change: "Cynics on the Internet (and they abound) list procedures that artificially raise the value of the buffer cache hit ratio and use this information to discredit the use of the counter as a diagnostic tool. Here is one such procedure:" To: "Cynics on the Internet (and they abound) list procedures that artificially raise the value of the buffer cache hit ratio and use this information to discredit the use of the counter as a diagnostic tool. Here is one such procedure (Note that this is not valid SQL Server code, and is only intended as an example):" |
Microsoft Press | May 06, 2010 | |
Printed | Page 313 |
Operating system referenced in place of SQL Server 2005 instance On page 313, the second bullet point reads: "Prior to beginning the test, ensure that the same hotfixes, service packs, and security updates that are installed on the production computer’s operating system are also installed on the test computer’s SQL Server 2005 instance." It should read: "Prior to beginning the test, ensure that the same hotfixes, service packs, and security updates that are installed on the production computer’s SQL Server 2005 instance are also installed on the test computer’s SQL Server 2005 instance." |
Microsoft Press | May 06, 2010 | |
Printed | Page 394 |
Negative incorrectly included in review question On page 394, the last sentence of question 2 reads: "When Ian creates a package and configures the package protection level, which of the following settings should he not use to ensure that Orin doesn’t have to re-enter sensitive values when he opens the package?" It should read: "When Ian creates a package and configures the package protection level, which of the following settings should he use to ensure that Orin doesn’t have to re-enter sensitive values when he opens the package?" |
Microsoft Press | May 06, 2010 | |
Printed | Page 516 |
UNIQUE constraint referenced in place of DISTINCT On page 516, answer A to question 1 reads: "A SELECT clause with a UNIQUE constraint" It should read: "A SELECT clause with a DISTINCT constraint" |
Microsoft Press | May 06, 2010 |