Errata
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 CD-ROM |
Updated sample files for chapter 8 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page xvii |
Incorrect sample file |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 17 |
Note should be added to step 2 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 146 |
Adapter should be adapter |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 162 |
Cha06-InitialCode should be Chap06 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 164 |
DEFAULT 0 should not be in code sample |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 170 |
Chapter06_03-ActiveX should be Chap06 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 197 |
Line break missing from code sample |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 203 |
project should be package |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 206 |
ConnectString should be ConnectionString |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 208 |
SSIS should be NewProducts.dtsConfig |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 212 |
database should be system |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 213 |
close BIDS should be on the File menu click Exit |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 216 |
In BIDS should be added to step 10 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 217 |
Step 8 should be changed |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 221 |
Additional information needed in the Using the SQL Server Import and Export Wizard to Execute Packages section |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 221 |
Additional information is needed in the note for step 3 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 225 |
Additional instruction needed in step 8 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 228 |
Step 2 should be more specific |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 231 |
navigate to should be enter |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 232 |
Additonal instruction needed in step 3 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 232 |
Steps 10 and 11 should be removed |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 232 |
Steps 10 and 11 should be removed |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 234 |
Step 4 should be more specific |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 424 |
Sample file not required |
Microsoft Press | Jul 13, 2010 | |
Other Digital Version | CD-ROM |
Extra command in sample code The last line in the file Chap06Chapter06_01_Script.txt is not needed. Remove: con.Close() |
Microsoft Press | May 06, 2010 | |
Other Digital Version | CD-ROM |
Incorrect answer sets for chapters 13 and 14 |
Microsoft Press | May 06, 2010 | |
Printed | Page xviii |
Alternate sample code location needed On page xviii, the second sentence needs additional information regarding using the sample code in Windows Vista. Change: "The default installation folder is C:Documents and Settings\My DocumentsMicrosoft Pressis2005sbs, where is the logon name you use to operate your computer." To: "The default installation folder is C:Documents and Settings\My DocumentsMicrosoft Pressis2005sbs, or C:Users\DocumentsMicrosoft Pressis2005sbs if you are using Windows Vista where is the logon name you use to operate your computer." |
Microsoft Press | May 06, 2010 | |
Printed | Page 143 |
Line break missing in code sample On page 143, the second line of the code sample in step 16 is missing a line break. Change: Imports System.IO Imports System.Data.SqlClientTo: Imports System.IO Imports System.Data.SqlClient |
Microsoft Press | May 06, 2010 | |
Printed | Page 160 |
Export Employees should be Set ExportFileName On page 160, the name in step 3 is incorrect. Change: "Double-click the new Script task. In the Script Task Editor dialog box, change the name to Script Task – Export Employees." To: "Double-click the new Script task. In the Script Task Editor dialog box, change the name to Script Task – Set ExportFileName." |
Microsoft Press | May 06, 2010 | |
Printed | Page 163 |
Incorrect screenshots On page 163, the two screenshots are incorrect and should be disregarded. |
Microsoft Press | May 06, 2010 | |
Printed | Page 168 |
Chap06_02 should be Chap06 On page 168, the path in step 23 is incorrect.Change: "C:Documents and Settings\My DocumentsMicrosoft Pressis2005SbSChap06_02Data" To: "C:Documents and Settings\My DocumentsMicrosoft Pressis2005SbSChap06Data" |
Microsoft Press | May 06, 2010 | |
Printed | Page 171 |
Chap06Chapter06_03-ActiveX should be Chap06 On page 171, in the first sentence after the code sample contains an incorrect path. Change: "This script is available in the text file saved in C:Documents and Settings\My DocumentsMicrosoft PressChap06Chapter06_03-ActiveX Chapter06_03_AXScript.txt." To: "This script is available in the text file saved in C:Documents and Settings\My DocumentsMicrosoft PressChap06Chapter06_03_AXScript.txt." |
Microsoft Press | May 06, 2010 | |
Printed | Page 203 |
Additional step needed between steps 3 and 4 On page 203, an additional step should be added between steps 3 and 4 that reads: "If you have not completed all exercises in the previous chapters then: a) In Solution Explorer find the Initialize.dtsx file under the SSIS Packages folder. Right-click Initialize.dtsx and click Execute Package. The Initialize.dtsx package will open in designer mode and execute. The package creates the QuickStartODS database and ProductNames table if they do not already exist. b) When the package finishes executing, on the Debug menu click Stop Debugging. Close the package." |
Microsoft Press | May 06, 2010 | |
Printed | Page 204 |
Additional instruction needed in step 8 On page 204, additional instructions are needed in step 8. Change: "Double-click ProductsDestination.txt. Notice that there are 62 records in the QuickStartODS database ProductNames table." To: "Double-click ProductsDestination.txt. Notice that there are 62 records in the file. Close the file. Open SQL Server Management Studio. Connect to the database engine on LocalHost. In Object Explorer expand LocalHost, Databases, QuickStartODS, Tables. Right-click the ProductNames table and click Open Table. Notice that there are 62 records in the QuickStartODS database ProductNames table." |
Microsoft Press | May 06, 2010 | |
Printed | Page 207 |
SSIS should be the NewProducts.dtsConfig - Microsoft Visual Studio window On page 207, the first sentence of step 3 is incorrect. Change: "In SSIS, on the NewProducts.dtsConfig tab, find in the XML file:" To: "In the NewProducts.dtsConfig – Microsoft Visual Studio window, on the NewProducts.dtsConfig tab, find in the XML file:" |
Microsoft Press | May 06, 2010 | |
Printed | Page 208 |
Additional step needed in the Testing the Package with the New Configuration section On page 208, an additional step needs to be added to the end of the "Testing the Package with the New Configuration" section that reads: "7. Switch to BIDS. On the Debug menu, click Stop Debugging." |
Microsoft Press | May 06, 2010 | |
Printed | Page 213 |
Additional instruction needed in step 8 On page 213, step 8 needs an additional instruction. Change: "Click OK to close the System Properties dialog box." To: "Click OK to close the System Properties dialog box. Close the My Computer window." |
Microsoft Press | May 06, 2010 | |
Printed | Page 216 |
Additional instruction needed in step 9 On page 216, additional instructions are needed in step 9. Change: "In the Package Configuration Wizard, verify that a table named [dbo].[SSIS Configurations] was created in the ConfigDB database and listed in the Configuration Table dropdown list." To: "In the Package Configuration Wizard, verify that a table named [dbo].[SSIS Configurations] is listed in the Configuration table drop-down list. In Management Studio verify that a table named dbo.SSIS Configurations was created in the ConfigDB database." |
Microsoft Press | May 06, 2010 | |
Printed | Page 217 |
Step 17 should be more specific On page 217, step 17 should be more specific. Change: "On the Table – dbo.SSIS Configurations tab, in the ConfiguredValue column, click NewProducts.txt, and then change the name to NewProductsShortList.txt." To: "On the Table – dbo.SSIS Configurations tab, in the ConfiguredValue column you will find the full path for the NewProducts.txt file. Change NewProducts.txt to NewProductsShortList.txt." |
Microsoft Press | May 06, 2010 | |
Printed | Page 219 |
parent package should be parent package variable configuration On page 219, the "Create the ParentProductsDestination parent package" header needs more information. Change: "Create the ParentProductsDestination parent package" To:"Create the ParentProductsDestination parent package variable configuration" |
Microsoft Press | May 06, 2010 | |
Printed | Page 221 |
Additional instruction needed in step 1 a On page 221, step 1 a needs additional information. Change: "On the File menu, click New, and then click New Project." To: "On the File menu, click New, and then click New Project. In the New Project dialog box, Templates pane, verify that Integration Services Project is selected." |
Microsoft Press | May 06, 2010 | |
Printed | Page 224 |
Additional information needed in the Execute tasks and containers and then disable the task and execute the package section On page 224, a paragraph should be added before step 1 in the "Execute tasks and containers and then disable the task and execute the package" section that reads: "When you are developing or debugging a package, you may want to execute the package one task or container at a time or you may want to execute all of the package except for a particular task or container. The following procedure will demonstrate how to do this." |
Microsoft Press | May 06, 2010 | |
Printed | Page 226 |
Step 2 should be more specific On page 226, the second sentence of step 2 should be more specific. Change: "In BIDS, on the XPkgUNewProducts.dtsConfig tab, between the tags, notice that the name of the destination file has been changed to XPkgUProductsDestination.txt." To: "In the XpkgUNewProducts.dtsConfig – Microsoft Visual Studio window, on the XpkgUNewProducts.dtsConfig tab, between the tags, notice that the name of the destination file is XpkgUProductsDestination.txt Close the XpkgUNewProducts.dtsConfig – Microsoft Visual Studio window." |
Microsoft Press | May 06, 2010 | |
Printed | Page 230 |
The description of the practice should be more specific On page 230, the sentence of the "Configuring Package Logging" section should be more specific. Change: "In this procedure, you will use the SSIS Log Provider for SQL Server to configure the package." To: "In this procedure, you will configure the package to write log entries using the SSIS Log Provider for Text Files and the SSIS Log Provider for SQL Server." |
Microsoft Press | May 06, 2010 | |
Printed | Page 232 |
Additional instruction needed in step 2 On page 232, step 2 of the "Execute the package and view the logs" section needs an additional instruction. Change: "In Windows Explorer, open the C:Documents and Settings\My DocumentsMicrosoft Pressis2005sbsChap08LogsPackageText.log file and view the log entries." To: "In Windows Explorer, open the C:Documents and Settings\My DocumentsMicrosoft PressIS2005SBSchap08LogsPackageText.log file and view the log entries. Close the file." |
Microsoft Press | May 06, 2010 | |
Printed | Page 232 |
navigate to should be enter On page 232, step 8 says "navigate to" rather than "enter". Change: "In the File text box, navigate to C:Documents and Settings\My DocumentsMicrosoft Pressis2005sbsChap08LogsClearMatchedNames.log." To: "In the File text box, enter C:Documents and Settings\My DocumentsMicrosoft PressIS2005SBSchap08LogsClearMatchedNames.log." |
Microsoft Press | May 06, 2010 | |
Printed | Page 232 |
navigate to should be enter On page 232, step 8 says "navigate to" rather than "enter". Change: "In the File text box, navigate to C:Documents and Settings\My DocumentsMicrosoft Pressis2005sbsChap08LogsClearMatchedNames.log." To: "In the File text box, enter C:Documents and Settings\My DocumentsMicrosoft PressIS2005SBSchap08LogsClearMatchedNames.log." |
Microsoft Press | May 06, 2010 | |
Printed | Page 233 |
Additional instruction needed in step 1 On page 233, the second sentence of step 1 should have additional instructions. Change: "Wait until the package has executed successfully." To: "Wait until the package has executed successfully and then on the Debug menu click Stop Debugging." |
Microsoft Press | May 06, 2010 | |
Printed | Page 234 |
Additional step needed On page 234, an additional step is needed after step 4 that reads: "5. Close the PackageText.log and ClearMatchedNames.log files. Exit Management Studio and BIDS." |
Microsoft Press | May 06, 2010 | |
Printed | Page 428 |
Incorrect database source names used On page 428, the DB source listed in steps 14 and 25 are incorrect. In step 14, change: "Connect the Employees OLE DB Source to the new Row Count by dragging the green arrow from the source to the transformation." To: "Connect the Resellers OLE DB Source to the new Row Count by dragging the green arrow from the source to the transformation." In step 25, change: "Connect the Employees OLE DB Source to the new Row Count by dragging the green arrow from the source to the transformation." To: "Connect the Territories OLE DB Source to the new Row Count by dragging the green arrow from the source to the transformation." 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. |
Microsoft Press | May 06, 2010 |