MORE INFORMATION
CD-ROM: Missing IDENTITY(1,1) property in \Practice Files\Chapter8\Lesson 1\CompleteLesson1.sql file
Line 84 in \Practice Files\Chapter8\Lesson 1\CompleteLesson1.sql reads:
ID INT NOT NULL,
It should read:
ID INT IDENTITY(1,1) NOT NULL,
Page 12: Mistake in memory limitation of SQL Server 2005 Workgroup Edition
On page 12, the third bullet point in the Memory requirements section reads:
"SQL Server 2005 Workgroup Edition: 512 MB; 1 GB or more recommended (maximum of 4 GB)"
It should read:
"SQL Server 2005 Workgroup Edition: 512 MB; 1 GB or more recommended (maximum of 3 GB)"
Page 13: Processor type named incorrectly
On page 13, under Processor requirements for 64-Bit Editions of SQL Server 2005 the 2nd bullet reads:
"X64 minimum: 1 GHz or faster AMD Opteron, AMD Athlon 64, Intel
Xenon with Intel EM64T support, or Intel Pentium IV with EM64T support"
It should read:
"X64 minimum: 1 GHz or faster AMD Opteron, AMD Athlon 64, Intel
Xeon with Intel EM64T support, or Intel Pentium IV with EM64T support"
Page 22: Local system account does have network access
On page 22, under the heading Built-In System Account or Domain User Account for the SQL Server and
SQL Server Agent Services? the first sentence in the 3rd paragraph reads:
"The local system account is a Windows OS account that has full administrative rights
on the local computer but has no network access rights."
It should read:
"The local system account is a Windows OS account that has full administrative rights
on the local computer."
Page 58: The description of the practice references a read-only filegroup, which is not created
On page 58, the final sentence on the page reads:
"In this practice, you will create a database that contains several files and filegroups and then configure one filegroup as the default filegroup and another as a read-only filegroup."
It should read:
"In this practice, you will create a database that contains several files and filegroups and then configure one filegroup as the default filegroup."
Page 84: Nesting roles are reversed
On page 84, the third sentence in the fourth paragraph reads:
"You could grant that role the permissions of the entire Accounting role by nesting Accounting within AccountingMgr and then just granting the extra manager permissions to the AccountingMgr role."
It should read:
"You could grant that role the permissions of the entire Accounting role by nesting AccountingMgr within Accounting and then just granting the extra manager permissions to the AccountingMgr role."
Page 97: Northwind database not found on CD-ROM
On page 97, step 1 under Creating a Microsoft Access Linked Server reads:
"1. Browse the companion CD and copy the \Practice File\Northwind.mdb database to C:\Practice Files\Northwind.mdb"
This file is not found on the CD-ROM, but can be download at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=06616212-0356-46a0-8da2-eebc53a68034&DisplayLang=en
Page 113: Explanation of the size declaration of character data types is incorrect
On page 113, the second and third sentence of the last paragraph read:
"When defining a character data type, you specify the maximum number of bytes the column is allowed to store. For example, a char(10) can store a maximum of 10 characters because each character requires one byte of storage, whereas an nchar(10) can store a maximum of five characters because each Unicode character requires two bytes of storage."
They should read:
"When defining a character data type, you specify the maximum number of characters the column is allowed to store."
Page 175: Object selected from subquery should be EmployeeID
On page 175, the first code sample on the page reads:
SELECT *
FROM HumanResources.Employee as E
WHERE E.EmployeeId IN
(
SELECT AddressID
FROM HumanResources.EmployeeAddress
)It should read:
SELECT *
FROM HumanResources.Employee as E
WHERE E.EmployeeId IN
(
SELECT EmployeeID
FROM HumanResources.EmployeeAddress
)Page 367: AFTER triggers can only be created on tables
On page 367, the last sentence in the third paragraph reads:
" And you can create any number of AFTER triggers on a view or table."
It should read:
" And you can create any number of AFTER triggers on a table."
Page 368: INSERTED and DELETED tables can be viewed with OUTPUT clause
On page 368, The second sentence in the second to last paragraph reads:
"INSERTED and DELETED tables are visible only within a trigger and cannot be accessed by any other contstruct such as a stored procedure or function."
It should read:
"INSERTED and DELETED tables can be viewed by using an OUTPUT clause."
Page 423: BACKUP LOG command backs up transaction log
On page 423, the last step in practice 1 reads:
"9. Execute the following command to perform a full database backup to the specified disk location:
BACKUP LOG AdventureWorks TO DISK = 'C:\TEST\AW2.TRN'"
It should read:
"9. Execute the following command to perform a full transaction log backup to the specified disk location:
BACKUP LOG AdventureWorks TO DISK = 'C:\TEST\AW2.TRN'"
Page 595: blocking_process_id referenced in place of blocking_session_id
On page 595, the code sample reads:
SELECT session_id, sql_handle, plan_handle FROM sys.dm_exec_requests WHERE
blocking_process_id > 0
It should read:
SELECT session_id, sql_handle, plan_handle FROM sys.dm_exec_requests WHERE
blocking_session_id > 0
Page 683: Default behavior for Standby mode misrepresented
On page 683, Answer C to Question 2 reads:
"This is the default behavior for the Standby mode. Using SSMS, clear the Disconnect Users In The Database When Restoring Backups check box of the log shipping configuration."
It should read:
"This is optional behavior for the Standby mode. Using SSMS, clear the Disconnect Users In The Database When Restoring Backups check box of the log shipping configuration."
Page 832: Search term missing from the second code sample
On page 832, the second code sample reads:
SELECT ProductDescriptionID, Description FROM Production.ProductDescription
WHERE CONTAINS(Description, N'');
It should read:
SELECT ProductDescriptionID, Description FROM Production.ProductDescription
WHERE CONTAINS(Description, N'bike');
Page 879: sys.dm_db_index_physical-stats referenced in place of sys.dm_db_index_physical_stats in the answers to Chapter 12, Case Scenario 1
On page 879, the answers to Case Scenario 1 read:
"1. SQL Server 2005 exposes index fragmentation levels through the sys.dm_db_index_physical-stats DMF. Your job should call this DMF to check for index fragmentation and determine whether it needs to perform any operations to defragment indexes.
2. Your job should check for external fragmentation by looking for values over 10 percent in the avg_fragmentation_in_percent column returned by the sys.dm_db_index_physical-stats DMF.
3. Your job should check for internal fragmentation by looking for values under 75 percent in the avg_page_space_used_in_percent column returned by the sys.dm_db_index_physical-stats DMF."
They should read:
"1. SQL Server 2005 exposes index fragmentation levels through the sys.dm_db_index_physical_stats DMF. Your job should call this DMF to check for index fragmentation and determine whether it needs to perform any operations to defragment indexes.
2. Your job should check for external fragmentation by looking for values over 10 percent in the avg_fragmentation_in_percent column returned by the sys.dm_db_index_physical_stats DMF.
3. Your job should check for internal fragmentation by looking for values under 75 percent in the avg_page_space_used_in_percent column returned by the sys.dm_db_index_physical_stats DMF."
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.