Errata
Book Preface
Microsoft changed the links to the SQL Server 2008 databases. Please read the post titled Software Prerequisites (the first sticky post) on the book discussion list for the correct URLs.
Chapter 2, page 45
Instead of:
Each new instance requires a separate SQL Server license…
Should be:
In 2007, Microsoft introduced special virtualization and multi-instancing licensing models which may not require a separate license per instance. Specifically, if you are installing multiple instances of SQL Server on the one box, there is no extra licenses required as long as if the server is licensed per processor and/or appropriate server/cal licenses are in place for the devices/users accessing the additional instance. With regards to installing any of the services on a different server, this requires a separate SQL Server licenses, either processor or server/cal. Please consult with your reseller about the most cost-effective SQL Server 2008 licensing model based on your specific requirements.
Chapter 2, page 55
Instead of:
…in preparation for upgrading to SQL Server 2005…
Should be:
…in preparation for upgrading to SQL Server 2008…
Chapter 4, page 135
Instead of:
The second dataset, DataSet1, reads…
Should be:
The second dataset, DataSet2, reads…
Chapter 4, page 161
Instead of:
<DefaultValue>1<DefaultValue>
Should be:
<DefaultValue>11000<DefaultValue>, since the AdventureWorks2008 database doesn’t have a customer with ID of 1.
Instead of:
7. In the Report Data window, double-click the CustomerID parameter. In the Parameters tab of the Dataset Properties window, verify that the CustomerID query parameter is linked to the CustomerID report parameter.
Should be:
7. In the Report Data window, create a new CustomerID parameter and configure its default and available values. Double-click the SalesOrder dataset to open its properties. In the Parameters tab, click the Add button and associate the customerID query parameter with the CustomerID report parameter.
Chapter 5, page 196, step 2
Open the Sales Order dataset in design mode and add the SalesOrderID column from the SalesOrderHeader table in the Products dataset query
Should be:
Open the Sales Order dataset in design mode and add the SalesOrderID column from the SalesOrderHeader table in the SalesOrder dataset query.
Chapter 5, page 200, section 5.4.2
Instead of:
=(Fields!InternetDiscountAmount.Value+Fields!ResellerDiscountAmount.Value)=0 Consequently, the column will be shown only on those pages where there is at least one row with a discount value greater than zero.
Should be:
=SUM(Fields!InternetDiscountAmount.Value+Fields!ResellerDiscountAmount.Value)=0 Consequently, the column will be hidden if the Discount field in all rows is zero.
Chapter 6, page 220, step 5
Instead of:
Select the Label Format tab …
Should be:
Select the Numbers tab …
Chapter 7, page 269
Instead of:
As exlained in this blog, the custom code for the Calculate Median report is not thread-safe.
Should be:
As of 7/2/09, the downloadable book code includes code changes to the Calculate Median report to make the code thread-safe.
Chapter 17, page 619, Figure 17.13
Instead of:
TargetServerURL: http://millennia02/reportserver
Should be:
http://millennia02
To be more accurate, Table 17.3 should specify http://<site> as TargetServerURL as well. When the report server is configured for SharePoint integration mode, the TargetServerURL setting specifies the SharePoint site URL. Notice that the TargetServerURL context description in BIDS is wrong as well.
Index
Instead of:
Printer Delivery Extension 692
Should be:
Printer Delivery Extension 691
