Errata for MCTS Self-Paced Training Kit (Exam 70-448): Microsoft® SQL Server® 2008 Business Intelligence Development and Maintenance
Submit your own errata for this product.
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 67
Exercise 2, Step 6 |
This exercise does not work. The .xml file is not generated and the package does not runs at all displaying "Package execution complete...." message. Can someone please confirm this error.
Note from the Author or Editor: this is because the user does not have security rights to the c: drive. The text could be changed to c:\temp\DimCustomer_Checkpoint.xml (and make sure the temp directory exists)
|
Zafar Alam |
May 15, 2011 |
Nov 30, 2012 |
| Printed |
Page 73
Second sentence in the 'IMPORTANT" section |
Second sentence 'and comparing these two'
should read 'and comparing these to'
|
KC Thomsoon |
Sep 10, 2010 |
Mar 01, 2011 |
| Printed, PDF |
Page 78
step #5 |
The word "Success" needs to be changed to "Failure," making it read, "...change the Value drop-down list to Failure...." If this is not done, then the message box does not appear in step #11.
Note from the Author or Editor: Please change "Success" to "Failure"
|
Anonymous |
Dec 18, 2010 |
Mar 01, 2011 |
| Printed |
Page 90
first line of code in the first step |
"AdventureWorks" should be "AdventureWorks2008"
|
Microsoft Press |
May 06, 2010 |
Mar 01, 2011 |
| Printed |
Page 108
point number 4 |
Page 108 point number 4 of Determining which configuration type to use says that (in the last sentence) Registry Entry is one of those configurations that can not have multiple properties in one configuration. This is in contrast to what is mentioned earlier on page 99 in Table 3.1 Configuration Types
Note from the Author or Editor: this is an issue. Please change the text on pg 99, table 3-1 for Registry entry. Instead of "You can select multiple" change it to "You can only select one"
|
Anonymous |
Sep 06, 2012 |
Nov 30, 2012 |
| Printed |
Page 111
2nd paragraph |
The second sentence reads (uppercasing mine):
`... It performs like a conditional if statement or CAST statement....'
I believe that should be `case', not `cast'.
Note from the Author or Editor: confirm. Change cast to case
|
Yawar Amin |
May 08, 2012 |
Nov 30, 2012 |
| PDF |
Page 114
Exercise 2 Step 1 |
"promoted" should be "prompted"
Note from the Author or Editor: confirm. Change promoted to prompted
|
James Suciadi |
Jul 08, 2011 |
Nov 30, 2012 |
| Printed, PDF |
Page 114
Exercise 1 step 3. h. |
Does not require ".()" after "property".
Should read: "Select the check box next to the ConnectionString property, and then click Next."
Note from the Author or Editor: Please remove ().
|
Anonymous |
Jan 13, 2011 |
Mar 01, 2011 |
| PDF |
Page 116
Exercise 2 Step 5 |
"[SSIS Configuration]" should be "[SSIS Configurations]"
Note from the Author or Editor: confirm, please change
|
James Suciadi |
Jul 08, 2011 |
Nov 30, 2012 |
| Printed |
Page 117
|
Additional step needed between steps 8 and 9
On page 117, and additional step is needed between steps 8 and 9. The new step should read:
"Navigate to the ControlFlow tab and select the Foreach Loop container. In the Properties window, set DelayValidation to true."
|
Microsoft Press |
Jul 13, 2010 |
Mar 01, 2011 |
| PDF |
Page 119
First paragraph line 8 |
"SSIS through SSIS" should be "SSIS through SSMS"
Note from the Author or Editor: please correct
|
James Suciadi |
Jul 08, 2011 |
Nov 30, 2012 |
| PDF |
Page 155
Exercise 2 |
"DimCustomer.dtsx, has a package password set on it..."
it was MyPackage.dtsx that has package password set, DimCustomer.dtsx does not have package password set
Note from the Author or Editor: [EV] delete the following sentence:
“The package used, DimCustomer.dtsx, has a package password set on it from the Lesson 1 exercises, which will require entering it during the job configuration steps.”
|
James Suciadi |
Jul 08, 2011 |
Nov 30, 2012 |
| PDF |
Page 171
2nd Line |
“Follow these steps to set up a data source that points to the AdventureWorks2008 database”
database name is not correct. I think it should be
“Follow these steps to set up a data source that points to the AdventureWorksDW2008 database”
Note from the Author or Editor: please correct
|
Nirmal Ram P K |
Aug 01, 2011 |
Nov 30, 2012 |
| PDF |
Page 194
Point 23, Last paragraph |
The penultimate sentence reads "Rename the English Promotion Name attribute to Promotion Name...". However nowhere during this exercise does it tell you to include the English Promotion Name attribute.
Note from the Author or Editor: Remove these words "English Promotion Name attribute to Promotion Name and"
|
Anonymous |
Sep 15, 2010 |
Mar 01, 2011 |
| PDF |
Page 242
Half way down |
The explanation in the sentence before of some MDX expression refers to 2004 - "...filtered for calendar year 2004 only." Yet the MDX expression refers to 2003
Select [Measures].[Internet Sales Amount] on Columns,
[Product].[Category].Members on Rows
FROM [Adventure Works]
Where [Date].[Calendar Year].&[2003]
Note from the Author or Editor: Select [Measures].[Internet Sales Amount] on Columns,
[Product].[Category].Members on Rows
FROM [Adventure Works]
Where [Date].[Calendar Year].&[2004]
|
Jude Agbro |
Sep 19, 2010 |
Nov 30, 2012 |
| Printed |
Page 250
. |
"A KPI has four main properties: Value, Goal, Status and Target"
I believe this should read
"A KPI has four main properties: Value, Goal, Status and Trend."
This revision would be consistent with page 226 and page 227.
Note from the Author or Editor: A KPI has four main properties: Value, Goal, Status and Trend.
|
Anonymous |
Aug 11, 2011 |
Nov 30, 2012 |
| Printed |
Page 347
fifth sentence in the first paragraph |
"Figure 8-19" should be "Figure 8-21"
Note from the Author or Editor:
|
Microsoft Press |
May 06, 2010 |
Mar 01, 2011 |
| Printed |
Page 397
|
"Input Group" should be "Income Group"
On page 397, the first sentence of the first paragraph includes an incorrect group name.
Change:
"In this example, you are predicting Input Group, using the Region column from the case table as input."
To:
"In this example, you are predicting Income Group, using the Region column from the case table as input."
Note from the Author or Editor:
Error corrected. Will be fixed in next printing.
|
Microsoft Press |
Jul 13, 2010 |
Mar 01, 2011 |
| Printed |
Page 438
Step 4 |
There is an error in step 4 of the exercise.
Instead the Sequence Clustering algorithm, the reader should select the Clustering algorithm.
Note from the Author or Editor: Note that in my book (first edition), the page is 404. In Exercise 3, step 4., the words
Microsoft Sequence Clustering
should be replaced with
Microsoft Clustering.
|
Anonymous |
Jan 31, 2013 |
|
| Printed |
Page 459
1st paragraph |
I don't think this is an error so much as a redundancy. In the SQL query used to get the data for the report, a couple of the join conditions are given twice:
INNER JOIN Purchasing.PurchaseOrderDetail AS pod ON p.ProductID = pod.ProductID AND p.ProductID = pod.ProductID
INNER JOIN Purchasing.PurchaseOrderHeader AS poh ON pod.PurchaseOrderID = poh.PurchaseOrderID AND pod.PurchaseOrderID = poh.PurchaseOrderID
Once for each should be enough.
Note from the Author or Editor: The reviewer is correct, there are two redundat join conditions. Please change the part of the query at the top of the page from
I
NNER JOIN Purchasing.PurchaseOrderDetail AS pod
ON p.ProductID = pod.ProductID
AND p.ProductID = pod.ProductID
INNER JOIN Purchasing.PurchaseOrderHeader AS poh
ON pod.PurchaseOrderID = poh.PurchaseOrderID
AND pod.PurchaseOrderID = poh.PurchaseOrderID
to
INNER JOIN Purchasing.PurchaseOrderDetail AS pod
ON p.ProductID = pod.ProductID
INNER JOIN Purchasing.PurchaseOrderHeader AS poh
ON pod.PurchaseOrderID = poh.PurchaseOrderID
(just delete the second conditions in the two ON clauses).
|
Yawar Amin |
May 03, 2012 |
Nov 30, 2012 |
| PDF |
Page 487
Point Number 3 |
= =RunningValue(Fields!BikeBuyer.Value,Sum,"Group1") should read =RunningValue(Fields!BikeBuyer.Value,Sum,"Group1") - i.e. the first '=' should be removed
Note from the Author or Editor: Remove first =
|
Jude Agbro |
Oct 05, 2010 |
Mar 01, 2011 |
| Printed, PDF |
Page 510
1st Paragraph of "Creating a Custom Assembly" |
Reads:
..\Source\Ch09\TK 448 Ch11 Custom Assembly\ folder
Correct location:
..\Source\Ch11\TK 448 Ch11 Custom Assembly\ folder
Note from the Author or Editor: The reviewer is correct, the folder reference is wrong. Please change the reference "\Source\Ch09\TK 448 Ch11 Custom Assembly\" to "\Source\Ch11\TK 448 Ch11 Custom Assembly\". This reference is in the first paragraph under the "Creating a Custom Assembly" title, at the bottom of the page 510.
|
Jeremiah |
May 08, 2012 |
Nov 30, 2012 |
| Printed |
Page 513
Exercise 1, Step 9 |
There is a typo in this step. The end should read as ...Finished Products Stock Level as the report name,...
Note from the Author or Editor: The reviewer is correct. Instead of
On the Completing The Wizard page, type Finished Products Stock Level as the product name, and then click Finish.
should be:
On the Completing The Wizard page, type Finished Products Stock Level as the report name, and then click Finish.
his is the text of the step 9 of exercise 1 at the top of the page.
|
Zafar Alam |
May 24, 2011 |
Nov 30, 2012 |
| Printed |
Page 513
Exercise 2, Step 9 |
Another typo on this page. Expression syntax is incorrect. There is double equality sign which is not correct. It should read as... =IIF(Fields!SafetyStockLevel.Value > Fields!StockLevel.Value,"White","Black")
Note from the Author or Editor: The reviewer is correct, one equality sign needs to be removed. Instead of
==IIF(Fields!SafetyStockLevel.Value > Fields!StockLevel.Value, "White", "Black")
should stand
=IIF(Fields!SafetyStockLevel.Value > Fields!StockLevel.Value, "White", "Black")
This code can be found in step 9. of the exercise at the bottom of the page.
|
Zafar Alam |
May 24, 2011 |
Nov 30, 2012 |
| PDF |
Page 515
Step 6 |
"[..] In the Class Name box, type ch11_customassembly.customcolor."
Must be "[..] In the Class Name box, type TK_488_Ch11_CustomAssembly.customcolor."
Otherwise the exercise won't work.
|
jomaweb |
Oct 31, 2010 |
Nov 30, 2012 |
| PDF |
Page 525
Exercise 3 - Step 10 |
Step 10 ends with:
"[...] Verify in SSMS that the model appears in the Models folder"
Must be:
"[...] Verify in REPORT MANAGER HOMEPAGE that the model appears in the Models folder"
Note from the Author or Editor: The reviewer is correct. Please change step 10 of Exercise 3 on page 525 from
Right-click the project name, and then click Deploy to deploy the report model. Verify in SSMS that the model appears in the Models folder.
to
Right-click the project name, and then click Deploy to deploy the report model. Verify in Report Manager that the model appears in the Models folder.
|
jomaweb |
Oct 31, 2010 |
Nov 30, 2012 |
|