Microsoft® SQL Server™ 2005 Integration Services Step by Step

Errata for Microsoft® SQL Server™ 2005 Integration Services Step by Step




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 The companion code for chapter 8 is incorrect. Corrected files are available for download from the Microsoft Download Center: IS2005SBS Chap8 Update.exe (http://download.microsoft.com/download/3/b/3/3b3e311c-360f-4699-bebf-ef62ba797b25/is2005sbs chap8 update.exe)

Microsoft Press  Jul 13, 2010 
Printed
Page xvii

Incorrect sample file The attach_databases.bat file located in the SetupQuesry section of the practice files does not function on some systems. A corrected version of the file is available for download from the Microsoft Download Center: attach_databases.exe (http://download.microsoft.com/download/3/b/3/3b3e311c-360f-4699-bebf-ef62ba797b25/attach_databases.exe

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 The answer sets for Chapters 13 and 14, located at IS2005SBSAnswersChap13 and IS2005SBSAnswersChap14 in the companion content, are incorrect. Corrected answer sets are available for download from the Microsoft Download Center: IS2005SBS Updated Answers.exe http://download.microsoft.com/download/3/b/3/3b3e311c-360f-4699-bebf-ef62ba797b25/is2005sbs updated answers.exe Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

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 17

Note should be added to step 2 On page 17, a note should be added to step 2 regaridng running BIDS as Administrator in Windows Vista. Change: "Double-click the SSIS Sample Solution.sln file. This opens the project in BIDS." To: "Double-click the SSIS Sample Solution.sln file. This opens the project in BIDS. NOTE: If you are running BIDS in Windows Vista, you will need to start BIDS by "Run as Administrator" when running the procedures in this book."

Microsoft Press  Jul 13, 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 146

Adapter should be adapter On page 146, adapter should not be capitalized in step 3. Change: "In the Code Editor, insert a new line before the Dim Adapter As New SqlDataAdapter line." To: "In the Code Editor, insert a new line before the Dim adapter As New SqlDataAdapter line."

Microsoft Press  Jul 13, 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 162

Cha06-InitialCode should be Chap06 On page 162, the first sentence of the last paragraph includes an incorrect path to the sample solution. Change: "Start BIDS and open the solution file saved under C:Documents and Settings\My DocumentsMicrosoft Pressis2005SbSChap06_02-InitialCode Chapter06_02.sln." To: "Start BIDS and open the solution file saved under C:Documents and Settings\My DocumentsMicrosoft Pressis2005SbSChap06Chapter06_02.sln."

Microsoft Press  Jul 13, 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 164

DEFAULT 0 should not be in code sample On page 164, the code sample in step 3 is incorrect. Change: ALTER TABLE is2005sbsDW.dbo.DimCustomer ADD IsValidEmail bit NULL DEFAULT 0To: ALTER TABLE is2005sbsDW.dbo.DimCustomer ADD IsValidEmail bit NULL

Microsoft Press  Jul 13, 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 170

Chapter06_03-ActiveX should be Chap06 On page 170, there is an incorrect path in the first sentence of step 4. Change: "In the Location text box, specify C:Documents and Settings\My DocumentsMicrosoft Pressis2005SbSChapter06_03-ActiveX." To: "In the Location text box, specify C:Documents and Settings\My DocumentsMicrosoft Pressis2005SbSChap06."

Microsoft Press  Jul 13, 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 197

Line break missing from code sample On page 197, the first code sample on the page is missing a line break. Change: Debug.WriteLine(String.Format("{0}: {1}", _ .Columns(col).ColumnName, .Columns(col))) To: Debug.WriteLine(String.Format("{0}: {1}", _ .Columns(col).ColumnName, .Columns(col)))

Microsoft Press  Jul 13, 2010 
Printed
Page 203

project should be package On page 203, the third and fourth sentences of step 4 reference project rather than package. Change: "You have now opened the project. It’s time to execute the project." To: "You have now opened the package in designer mode. It’s time to execute the package."

Microsoft Press  Jul 13, 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 206

ConnectString should be ConnectionString On page 206, step 7 b refers to ConnectString rather than ConnectionString. Change: "Select the ConnectString check box." To: "Select the ConnectionString check box."

Microsoft Press  Jul 13, 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

SSIS should be NewProducts.dtsConfig On page 208, step 7 references SSIS instead of NewProducts.dtsConfig. Change: "Close the SSIS file." To: "Close the NewProducts.dtsConfig file."

Microsoft Press  Jul 13, 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 212

database should be system On page 212, the first sentence of the "Creating the Environment Variable" sections references a database environment variable rather than s system environment variable. Change: "In this procedure, you’ll create a database environment variable named ConfigDBName." To: "In this procedure, you’ll create a system environment variable named ConfigDBName."

Microsoft Press  Jul 13, 2010 
Printed
Page 213

close BIDS should be on the File menu click Exit On page 213, step 9 should be more specific. Change: "In BIDS, on the File menu, click Save All, and then close BIDS." To: "In BIDS, on the File menu, click Save All, then on the File menu click Exit."

Microsoft Press  Jul 13, 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

In BIDS should be added to step 10 On page 216, the first sentence of step 10 should be more specific. Change: "In the Configuration Filter drop-down list, type ProductsShortListFilter, and then click Next." To: "In BIDS, in the Configuration Filter drop-down list, type ProductsShortListFilter, and then click Next. The Select Properties To Export page appears."

Microsoft Press  Jul 13, 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 8 should be changed On page 217, the second sentence of step 8 should be changed. Change: "On the Table – dbo.ProductNames tab, SQL populates the table with data." To: "The execute SQL command refreshes the data displayed in the Table – dbo.PopulateNames window."

Microsoft Press  Jul 13, 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 information needed in the Using the SQL Server Import and Export Wizard to Execute Packages section On page 221, the first paragraph of the "Using the SQL Server Import and Export Wizard to Execute Packages" section should be changed. Change: "The SQL Server Import and Export Wizard provides the simplest method for creating and executing a simple package. You can start the SQL Server Import and Export Wizard from an Integrations Services package in BIDS, or you can start the wizard from SQL Server Management Studio; however, you can execute a package only if you start the SQL Server Import and Export Wizard in SQL Server Management Studio." To: "The SQL Server Import and Export Wizard provides the easiest method for creating and executing a simple package. You can start the SQL Server Import and Export Wizard from an Integrations Services project in BIDS or you can start the wizard from SQL Server Management Studio. There is a slight difference in the way the wizard functions when it is started from Management Studio versus when it is started from BIDS. If you start the wizard in Management Studio you are given an option to have the package executed when the wizard finishes. If you start the wizard from BIDS the package will not be executed when the wizard finishes. Instead, the wizard finishes and the package is saved in your Integration Services project. You may then execute the package from BIDS by right-clicking on the package and clicking Execute Package. To start the SQL Server Import and Export Wizard from BIDS in Solution Explorer right-click on the SSIS Packages folder and click SSIS Import and Export Wizard. To start the wizard from Management Studio right-click on a database, click Tasks, and then click Import Data or click Export Data. An exercise demonstrating how to use the SQL Server Import and Export Wizard is included in the “Using the SSIS Import and Export Wizard” section in Chapter 2."

Microsoft Press  Jul 13, 2010 
Printed
Page 221

Additional information is needed in the note for step 3 On page 221, the note in step 3 of the "Start the SQL Server Wizard from BIDS" section needs more information. Change: "A package cannot be executed if you start the SQL Server Import And Export Wizard from an Integrations Services package in BIDS." To: "If you start the SQL Server Import and Export Wizard from an Integration Services project in BIDS the wizard will not execute the package. Once the wizard is finished, right-click on the package and click Execute Package."

Microsoft Press  Jul 13, 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 225

Additional instruction needed in step 8 On page 225, additional instructions should be added to step 8. Change: "On the Control Flow tab, right-click Foreach Loop Container – FuzzyInput Files, and then click Disable." To: "On the Control Flow tab, right-click Foreach Loop Container – FuzzyInput Files, and then click Disable. In Windows Explorer, delete the C:Documents and Settings\My DocumentsMicrosoft PressIS2005SBSchap08DataXMLProductsDestination.txt file."

Microsoft Press  Jul 13, 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 228

Step 2 should be more specific On page 228, step 2 should include more specific instruction. Change: "In the left pane, toward the bottom of the tree, right-click the SQL Server Agent folder, and then click Start." To: "In the Object Explorer, toward the bottom of the tree, right-click the SQL Server Agent folder, and then click Start. (If Start is disabled, then SQL Server Agent is already started, go to the next step.)"

Microsoft Press  Jul 13, 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 231

navigate to should be enter On page 231, step 10 says "navigate to" rather than "enter". Change: "In the File text box, navigate to C:Documents and Settings\My DocumentsMicrosoft Pressis2005sbsChap08LogsPackageText.log." To: "In the File text box, enter C:Documents and Settings\My DocumentsMicrosoft PressIS2005SBSchap08LogsPackageText.log."

Microsoft Press  Jul 13, 2010 
Printed
Page 232

Additonal instruction needed in step 3 On page 232, step 3 of the "Execute the package and view the logs" section needs additional instructions. Change: "In SQL Server Management Studio, in the left pane, expand Databases and QuickStartODS. Expand the Tables folder, and then right-click dbo.sysdtslog90 and click Open table. View the log entries." To: "In SQL Server Management Studio, in the left pane, expand Databases and expand QuickStartODS. Right-click on the Tables folder and click Refresh. Expand the Tables folder, and then right-click dob.sysdtslog90 and click Open Table. View the log entries."

Microsoft Press  Jul 13, 2010 
Printed
Page 232

Steps 10 and 11 should be removed On page 232, steps 10 and 11 are not needed and should be removed.

Microsoft Press  Jul 13, 2010 
Printed
Page 232

Steps 10 and 11 should be removed On page 232, steps 10 and 11 are not needed and should be removed.

Microsoft Press  Jul 13, 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

Step 4 should be more specific On page 234, step 4 should be more specific. Change: "Open the QuickStartODS database sysdtslog90 table and view the log entries." To: "In SQL Server Management Studio click on the Table – dbo.sysdtslog90 tab. On the toolbar, click the red exclamation mark (!) (Execute SQL). View the additional log entries."

Microsoft Press  Jul 13, 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 424

Sample file not required On page 424, the first and second steps under "Open project and build packages" refer to a sample file "Chp14.sln" which is not provided in the sample file installation folder. However, this file is not needed as the instructions provided in steps 2 through 6 create this file. Change: "1. Open the Chp14.sln project in the C:Documents and Settings\My Documents Microsoft Pressis2005sbsChap14 folder. 2. The following steps detail creating a new Integration Services Project. Click New, and then click Project from the BIDS File menu. If opening Chp14.sln, these steps will have been completed already. 3. Right-click Package.dtsx and rename this package MasterPackage.dtsx. 4. Right-click SSIS Packages and select New SSIS Package. Right-click this package, select Rename, and change the name to Child1.dtsx. 5. Right-click SSIS Packages and select New SSIS Package. Right-click this package, select Rename, and change the name to Child2.dtsx. 6. Right-click SSIS Packages and select New SSIS Package. Right-click this package, select Rename, and change the name to Child3.dtsx." To: "1. The following steps detail creating a new Integration Services Project. Click New, and then click Project from the BIDS File menu. 2. Right-click Package.dtsx and rename this package MasterPackage.dtsx. 3. Right-click SSIS Packages and select New SSIS Package. Right-click this package, select Rename, and change the name to Child1.dtsx. 4. Right-click SSIS Packages and select New SSIS Package. Right-click this package, select Rename, and change the name to Child2.dtsx. 5. Right-click SSIS Packages and select New SSIS Package. Right-click this package, select Rename, and change the name to Child3.dtsx."

Microsoft Press  Jul 13, 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