Errata

http://technet.microsoft.com/en-us/library/cc757143%28WS.10%29.aspx
Windows Server 2003 Standard Edition allows one to use NLB Clusters, but not MSCS clustering, which is required for clustering SQL Server.

(This is also important on page 408 when considering which operating system to use. Windows Server 2008 Standard Edition is fine for a two node cluster, fortunately.)

Note from the Author or Editor:
In Table 14-2, please remove the first entry for Windows Server 2003 Standard Edition. There is no replacement or other correction.

The line "Both global and local temporary tables are dropped automatically when the connection that created the tables is terminated." is incorrect.

It is true that local tables are dropped when the connection that created it is terminated. However, global temporary tables persist until all connections that are accessing it have been terminated, even when the connection that created it has long been terminated.

This is backed up by Books Online (http://msdn.microsoft.com/en-us/library/ms186986(v=SQL.100).aspx): "Local temporary tables are deleted after the user disconnects from the instance of SQL Server. Global temporary tables are visible to any user and any connection after they are created, and are deleted when all users that are referencing the table disconnect from the instance of SQL Server."

Note from the Author or Editor:
Page 74, last sentence of paragraph 3. Change "Both global and local temporary tables are dropped automatically when the connection that created the tables is terminated." to "Local temporary tables are dropped automatically when the connection that created them is terminated. Global temporary tables are dropped when the last connection using them is terminated."

In the practice section on page 29, the user is directed to execute the following command:

EXEC sp_configure 'Database Mail XPs', 1
GO
RECONFIGURE;
GO

This produced an error stating 'Database Mail XPs' did not exists.

After researching I discovered that the following steps have to be performed first.

sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO


The instructions should read as follows:
sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
EXEC sp_configure 'Database Mail XPs', 1
GO
RECONFIGURE;
GO

Note from the Author or Editor:
Page 29, practice. Change the T-SQL in step 1 to:

sp_configure 'show advanced options', 1;
GO
RECONFIGURE WITH OVERRIDE;
GO
EXEC sp_configure 'Database Mail XPs', 1
GO
RECONFIGURE WITH OVERRIDE;
GO

NOTE TO EDITOR. This adds 4 more lines within the pagination, which creates a bit of an issue in trying not to make major formatting changes. So, the following changes can also be made at your discretion to consolidate and keep everything on the same page that it currently is. Change step 2 to include the text from step 3. Combine Step 6 and 7 into a single step and renumber the steps appropriately.

The Bookings and Customers databases

instead of

The Orders and Customers databases

Note from the Author or Editor:
Page 548, Table 17-2. Change Bookings to Orders.

In step 40 lookup check box should be spelled with lower case l.

In figure 14-10 the Enable LMHOSTS lookup check box should be cleared.

Note from the Author or Editor:
Page 425, step 40. Change "LMHOSTS Lookup" to "LMHOSTS lookup".

Figure 14-10, "LMHOSTS lookup" checkbox cleared

SELECT DocumentSummary, Title, FileName FROM Production.Document

instead of

SELECT DocumentNode, Title, FileName FROM Production.Document

Note from the Author or Editor:
Not correctable as previously noted. The version of the AdventureWorks database has changed since the book was written and would require a major re-write to correct to the current version.

SELECT DocumentSummary, Title, FileName FROM Production.Document

instead of

SELECT DocumentNode, Title, FileName FROM Production.Document

Note from the Author or Editor:
Not correctable as previously noted. The version of the AdventureWorks database has changed since the book was written and would require a major re-write to correct to the current version.

GRANT VIEW DEFINITION TO <user>

If you grant VIEW ANY DEFINITION to a login,

instead of the obvious spelling errors.

Note from the Author or Editor:
Page 274. 3rd line. Code has an extraneous space in it. It should read "GRANT VIEW DEFINITION TO <user>"

CREATE DATABASE AdventureWorksSnap ON
(NAME = N'AdventureWorks_Data',

instead of N'AdventureWorks2008_Data',

Note from the Author or Editor:
Not correctable. These were the names of my database files, which differ from the current version of the AdventureWorks database on CodePlex. The reader can also change these names.

delete the AdventureWorks_Data.mdf file. Make certain that you do not delete the AdventureWorks_Log.ldf file.

The names of the files differ from the book.

Note from the Author or Editor:
Not correctable since the files names have changed within the CodePlex files currently available and the reader can change these names to anything that they want.

2. The FILLFACTOR option reserves space only on the leaf levels of the index.

and not on the intermediate levels as is emphasized on page 97.

Note from the Author or Editor:
Page 101. Quick Check answer #2. Remove the text "intermediate and".

CREATE NONCLUSTERED INDEX idx_employeefirstname

The s in firstname is missing

Note from the Author or Editor:
Page 147 T-SQL script in Creating a Partitioned Index section. Change "CREATE NONCLUSTERED INDEX idx_employeefirtname" to "CREATE NONCLUSTERED INDEX idx_employeefirstname"

FILENAME = 'c:\test\db.mdf', SIZE = 3 MB),

The primary file file must be at least 3 MB to accommodate a copy of the model database.

Note from the Author or Editor:
Page 140. Change "2MB" to "3MB".

Add the following sentence before step 1: Create a folder c:\test if it does not exist already.

Note from the Author or Editor:
Page 44. Practice. Change the first sentence to "In this practice, you will create a database with multiple files that is enabled for FILESTREAM storage in the c:\test folder.

Step 2 should read: 2. Navigate to the SQL Server 2008 product sample databases and download AdventureWorks2008_SR4.exe.

Note from the Author or Editor:
Page 25, step 2. Change "AdventureWorks2008*.msi" to "AdventureWorks2008_SR4.exe"

Step 8 comes after Step 9. The steps should change place.

Note from the Author or Editor:
Page 24. Change order of steps 8 and 9. Step 8 should be step 9. Step 9 should be step 8.

The character data type table lists maximum values for unicode and non-Unicode characters. Each data type (char,varchar,nchar and nvarchar) state "...up to a maximum of x bytes."

This is incorrect. The values listed are the maximum number of characters, not bytes. It should be changed to read:

"...up to a maximum of x characters."

Note from the Author or Editor:
Page 66, table 3-3. Change "bytes" to "characters".

Table 1-2 seems to disagree with this information on the Microsoft site:
http://www.microsoft.com/sqlserver/2008/en/us/editions.aspx

Note from the Author or Editor:
Page 12. Table 1-2. Change to the following:

# of CPUs
Standard: 4
Workgroup: 2
Express: 1
Compact: OS Maximum

Database Size
Standard: 524PB
Workgroup: 524PB
Express: 10GB
Compact: 4GB

RAM
Standard: 64GB
Workgroup: 4GB
Express: 1GB
Compact: OS Maximum