Microsoft KB Archive/943829

= Microsoft SQL Server 2005 Integration Services Step by Step comments and corrections =

Article ID: 943829

Article Last Modified on 10/16/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Integration Services Step by Step, ISBN 978-0-7356-2405-4

-



SUMMARY
This article contains comments, corrections, and information about known errors relating to the Microsoft Press book Microsoft SQL Server 2005 Integration Services Step by Step, 978-0-7356-2405-4.

The following topics are covered:


 * CD-ROM: Extra command in sample code
 * CD-ROM: Updated sample files for chapter 8
 * CD-ROM: Incorrect answer sets for chapters 13 and 14
 * Page xvii: Incorrect sample file
 * Page xviii: Alternate sample code location needed
 * Page 17: Note should be added to step 2
 * Page 143: Line break missing in code sample
 * Page 146: Adapter should be adapter
 * Page 160: Export Employees should be Set ExportFileName
 * Page 162: Cha06-InitialCode should be Chap06
 * Page 163: Incorrect screenshots
 * Page 164: DEFAULT 0 should not be in code sample
 * Page 168: Chap06_02 should be Chap06
 * Page 170: Chapter06_03-ActiveX should be Chap06
 * Page 171: Chap06\Chapter06_03-ActiveX should be Chap06
 * Page 197: Line break missing from code sample
 * Page 203: Additional step needed between steps 3 and 4
 * Page 203: project should be package
 * Page 204: Additional instruction needed in step 8
 * Page 206: ConnectString should be ConnectionString
 * Page 207: SSIS should be the NewProducts.dtsConfig - Microsoft Visual Studio window
 * Page 208: SSIS should be NewProducts.dtsConfig
 * Page 208: Additional step needed in the Testing the Package with the New Configuration section
 * Page 212: database should be system
 * Page 213: Additional instruction needed in step 8
 * Page 213: close BIDS should be on the File menu click Exit
 * Page 216: Additional instruction needed in step 9
 * Page 216: In BIDS should be added to step 10
 * Page 217: Step 17 should be more specific
 * Page 217: Step 8 should be changed
 * Page 219: parent package should be parent package variable configuration
 * Page 221: Additional information needed in the Using the SQL Server Import and Export Wizard to Execute Packages section
 * Page 221: Additional instruction needed in step 1 a
 * Page 221: Additional information is needed in the note for step 3
 * Page 224: Additional information needed in the Execute tasks and containers and then disable the task and execute the package section
 * Page 225: Additional instruction needed in step 8
 * Page 226: Step 2 should be more specific
 * Page 228: Step 2 should be more specific
 * Page 230: The description of the practice should be more specific
 * Page 231: navigate to should be enter
 * Page 232: Additional instruction needed in step 2
 * Page 232: Additonal instruction needed in step 3
 * Page 232: navigate to should be enter
 * Page 232: Steps 10 and 11 should be removed
 * Page 233: Additional instruction needed in step 1
 * Page 234: Step 4 should be more specific
 * Page 234: Additional step needed



CD-ROM: Extra command in sample code
The last line in the file \Chap06\Chapter06_01_Script.txt is not needed.

Remove: con.Close

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

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

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.

CD-ROM: Incorrect answer sets for chapters 13 and 14
The answer sets for Chapters 13 and 14, located at \IS2005SBS\Answers\Chap13 and \IS2005SBS\Answers\Chap14 in the companion content, are incorrect. Corrected answer sets are available for download from the Microsoft Download Center:

IS2005SBS Updated Answers.exe

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

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.

Page xvii: Incorrect sample file
The attach_databases.bat file located in the Setup\Quesry 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

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

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.

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:

&quot;The default installation folder is C:\Documents and Settings\ \My Documents\Microsoft Press\is2005sbs, where is the logon name you use to operate your computer.&quot;

To:

&quot;The default installation folder is C:\Documents and Settings\ \My Documents\Microsoft Press\is2005sbs, or C:\Users\ \Documents\Microsoft Press\is2005sbs if you are using Windows Vista where is the logon name you use to operate your computer.&quot;

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:

&quot;Double-click the SSIS Sample Solution.sln file. This opens the project in BIDS.&quot;

To:

&quot;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 &quot;Run as Administrator&quot; when running the procedures in this book.&quot;

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.SqlClient

To: Imports System.IO Imports System.Data.SqlClient

Page 146: Adapter should be adapter
On page 146, adapter should not be capitalized in step 3.

Change:

&quot;In the Code Editor, insert a new line before the Dim Adapter As New SqlDataAdapter line.&quot;

To:

&quot;In the Code Editor, insert a new line before the Dim adapter As New SqlDataAdapter line.&quot;

Page 160: Export Employees should be Set ExportFileName
On page 160, the name in step 3 is incorrect.

Change:

&quot;Double-click the new Script task. In the Script Task Editor dialog box, change the name to Script Task – Export Employees.&quot;

To:

&quot;Double-click the new Script task. In the Script Task Editor dialog box, change the name to Script Task – Set ExportFileName.&quot;

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:

&quot;Start BIDS and open the solution file saved under C:\Documents and Settings\ \My Documents\Microsoft Press\is2005SbS\Chap06_02-InitialCode \Chapter06_02.sln.&quot;

To:

&quot;Start BIDS and open the solution file saved under C:\Documents and Settings\ \My Documents\Microsoft Press\is2005SbS\Chap06\Chapter06_02.sln.&quot;

Page 163: Incorrect screenshots
On page 163, the two screenshots are incorrect and should be disregarded.

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 0

To: ALTER TABLE is2005sbsDW.dbo.DimCustomer ADD IsValidEmail bit NULL

Page 168: Chap06_02 should be Chap06
On page 168, the path in step 23 is incorrect.

Change:

&quot;C:\Documents and Settings\ \My Documents\Microsoft Press\is2005SbS\Chap06_02\Data&quot;

To:

&quot;C:\Documents and Settings\ \My Documents\Microsoft Press\is2005SbS\Chap06\Data&quot;

Page 170: Chapter06_03-ActiveX should be Chap06
On page 170, there is an incorrect path in the first sentence of step 4.

Change:

&quot;In the Location text box, specify C:\Documents and Settings\ \My Documents\Microsoft Press\is2005SbS\Chapter06_03-ActiveX.&quot;

To:

&quot;In the Location text box, specify C:\Documents and Settings\ \My Documents\Microsoft Press\is2005SbS\Chap06.&quot;

Page 171: Chap06\Chapter06_03-ActiveX should be Chap06
On page 171, in the first sentence after the code sample contains an incorrect path.

Change:

&quot;This script is available in the text file saved in C:\Documents and Settings\ \My Documents\Microsoft Press\Chap06\Chapter06_03-ActiveX \Chapter06_03_AXScript.txt.&quot;

To:

&quot;This script is available in the text file saved in C:\Documents and Settings\ \My Documents\Microsoft Press\Chap06\Chapter06_03_AXScript.txt.&quot;

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(&quot;{0}: {1}&quot;, _ .Columns(col).ColumnName, .Columns(col))) To: Debug.WriteLine(String.Format(&quot;{0}: {1}&quot;, _ .Columns(col).ColumnName, .Columns(col)))

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:

&quot;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.&quot;

Page 203: project should be package
On page 203, the third and fourth sentences of step 4 reference project rather than package.

Change:

&quot;You have now opened the project. It’s time to execute the project.&quot;

To:

&quot;You have now opened the package in designer mode. It’s time to execute the package.&quot;

Page 204: Additional instruction needed in step 8
On page 204, additional instructions are needed in step 8.

Change:

&quot;Double-click ProductsDestination.txt.

Notice that there are 62 records in the QuickStartODS database ProductNames table.&quot;

To:

&quot;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.&quot;

Page 206: ConnectString should be ConnectionString
On page 206, step 7 b refers to ConnectString rather than ConnectionString.

Change:

&quot;Select the ConnectString check box.&quot;

To:

&quot;Select the ConnectionString check box.&quot;

Page 207: SSIS should be the NewProducts.dtsConfig - Microsoft Visual Studio window
On page 207, the first sentence of step 3 is incorrect.

Change:

&quot;In SSIS, on the NewProducts.dtsConfig tab, find  in the XML file:&quot;

To:

&quot;In the NewProducts.dtsConfig – Microsoft Visual Studio window, on the NewProducts.dtsConfig tab, find  in the XML file:&quot;

Page 208: SSIS should be NewProducts.dtsConfig
On page 208, step 7 references SSIS instead of NewProducts.dtsConfig.

Change:

&quot;Close the SSIS file.&quot;

To:

&quot;Close the NewProducts.dtsConfig file.&quot;

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 &quot;Testing the Package with the New Configuration&quot; section that reads:

&quot;7. Switch to BIDS. On the Debug menu, click Stop Debugging.&quot;

Page 212: database should be system
On page 212, the first sentence of the &quot;Creating the Environment Variable&quot; sections references a database environment variable rather than s system environment variable.

Change:

&quot;In this procedure, you’ll create a database environment variable named ConfigDBName.&quot;

To:

&quot;In this procedure, you’ll create a system environment variable named ConfigDBName.&quot;

Page 213: Additional instruction needed in step 8
On page 213, step 8 needs an additional instruction.

Change:

&quot;Click OK to close the System Properties dialog box.&quot;

To:

&quot;Click OK to close the System Properties dialog box. Close the My Computer window.&quot;

Page 213: close BIDS should be on the File menu click Exit
On page 213, step 9 should be more specific.

Change:

&quot;In BIDS, on the File menu, click Save All, and then close BIDS.&quot;

To:

&quot;In BIDS, on the File menu, click Save All, then on the File menu click Exit.&quot;

Page 216: Additional instruction needed in step 9
On page 216, additional instructions are needed in step 9.

Change:

&quot;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.&quot;

To:

&quot;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.&quot;

Page 216: In BIDS should be added to step 10
On page 216, the first sentence of step 10 should be more specific.

Change:

&quot;In the Configuration Filter drop-down list, type ProductsShortListFilter, and then click Next.&quot;

To:

&quot;In BIDS, in the Configuration Filter drop-down list, type ProductsShortListFilter, and then click Next. The Select Properties To Export page appears.&quot;

Page 217: Step 17 should be more specific
On page 217, step 17 should be more specific.

Change:

&quot;On the Table – dbo.SSIS Configurations tab, in the ConfiguredValue column, click NewProducts.txt, and then change the name to NewProductsShortList.txt.&quot;

To:

&quot;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.&quot;

Page 217: Step 8 should be changed
On page 217, the second sentence of step 8 should be changed.

Change:

&quot;On the Table – dbo.ProductNames tab, SQL populates the table with data.&quot;

To:

&quot;The execute SQL command refreshes the data displayed in the Table – dbo.PopulateNames window.&quot;

Page 219: parent package should be parent package variable configuration
On page 219, the &quot;Create the ParentProductsDestination parent package&quot; header needs more information.

Change:

&quot;Create the ParentProductsDestination parent package&quot;

To:

&quot;Create the ParentProductsDestination parent package variable configuration&quot;

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 &quot;Using the SQL Server Import and Export Wizard to Execute Packages&quot; section should be changed.

Change:

&quot;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.&quot;

To:

&quot;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.&quot;

Page 221: Additional instruction needed in step 1 a
On page 221, step 1 a needs additional information.

Change:

&quot;On the File menu, click New, and then click New Project.&quot;

To:

&quot;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.&quot;

Page 221: Additional information is needed in the note for step 3
On page 221, the note in step 3 of the &quot;Start the SQL Server Wizard from BIDS&quot; section needs more information.

Change:

&quot;A package cannot be executed if you start the SQL Server Import And Export Wizard from an Integrations Services package in BIDS.&quot;

To:

&quot;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.&quot;

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 &quot;Execute tasks and containers and then disable the task and execute the package&quot; section that reads:

&quot;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.&quot;

Page 225: Additional instruction needed in step 8
On page 225, additional instructions should be added to step 8.

Change:

&quot;On the Control Flow tab, right-click Foreach Loop Container – FuzzyInput Files, and then click Disable.&quot;

To:

&quot;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 Documents\Microsoft Press\IS2005SBS\chap08\Data\XMLProductsDestination.txt file.&quot;

Page 226: Step 2 should be more specific
On page 226, the second sentence of step 2 should be more specific.

Change:

&quot;In BIDS, on the XPkgUNewProducts.dtsConfig tab, between the  tags, notice that the name of the destination file has been changed to XPkgUProductsDestination.txt.&quot;

To:

&quot;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.&quot;

Page 228: Step 2 should be more specific
On page 228, step 2 should include more specific instruction.

Change:

&quot;In the left pane, toward the bottom of the tree, right-click the SQL Server Agent folder, and then click Start.&quot;

To:

&quot;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.)&quot;

Page 230: The description of the practice should be more specific
On page 230, the sentence of the &quot;Configuring Package Logging&quot; section should be more specific.

Change:

&quot;In this procedure, you will use the SSIS Log Provider for SQL Server to configure the package.&quot;

To:

&quot;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.&quot;

Page 231: navigate to should be enter
On page 231, step 10 says &quot;navigate to&quot; rather than &quot;enter&quot;.

Change:

&quot;In the File text box, navigate to C:\Documents and Settings\ \My Documents\Microsoft Press\is2005sbs\Chap08\Logs\PackageText.log.&quot;

To:

&quot;In the File text box, enter C:\Documents and Settings\ \My Documents\Microsoft Press\IS2005SBS\chap08\Logs\PackageText.log.&quot;

Page 232: Additional instruction needed in step 2
On page 232, step 2 of the &quot;Execute the package and view the logs&quot; section needs an additional instruction.

Change:

&quot;In Windows Explorer, open the C:\Documents and Settings\ \My Documents\Microsoft Press\is2005sbs\Chap08\Logs\PackageText.log file and view the log entries.&quot;

To:

&quot;In Windows Explorer, open the C:\Documents and Settings\ \My Documents\Microsoft Press\IS2005SBS\chap08\Logs\PackageText.log file and view the log entries. Close the file.&quot;

Page 232: Additonal instruction needed in step 3
On page 232, step 3 of the &quot;Execute the package and view the logs&quot; section needs additional instructions.

Change:

&quot;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.&quot;

To:

&quot;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.&quot;

Page 232: navigate to should be enter
On page 232, step 8 says &quot;navigate to&quot; rather than &quot;enter&quot;.

Change:

&quot;In the File text box, navigate to C:\Documents and Settings\ \My Documents\Microsoft Press\is2005sbs\Chap08\Logs\ClearMatchedNames.log.&quot;

To:

&quot;In the File text box, enter C:\Documents and Settings\ \My Documents\Microsoft Press\IS2005SBS\chap08\Logs\ClearMatchedNames.log.&quot;

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

Page 232: navigate to should be enter
On page 232, step 8 says &quot;navigate to&quot; rather than &quot;enter&quot;.

Change:

&quot;In the File text box, navigate to C:\Documents and Settings\ \My Documents\Microsoft Press\is2005sbs\Chap08\Logs\ClearMatchedNames.log.&quot;

To:

&quot;In the File text box, enter C:\Documents and Settings\ \My Documents\Microsoft Press\IS2005SBS\chap08\Logs\ClearMatchedNames.log.&quot;

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

Page 233: Additional instruction needed in step 1
On page 233, the second sentence of step 1 should have additional instructions.

Change:

&quot;Wait until the package has executed successfully.&quot;

To:

&quot;Wait until the package has executed successfully and then on the Debug menu click Stop Debugging.&quot;

Page 234: Step 4 should be more specific
On page 234, step 4 should be more specific.

Change:

&quot;Open the QuickStartODS database sysdtslog90 table and view the log entries.&quot;

To:

&quot;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.&quot;

Page 234: Additional step needed
On page 234, an additional step is needed after step 4 that reads:

&quot;5. Close the PackageText.log and ClearMatchedNames.log files. Exit Management Studio and BIDS.&quot;

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.

Additional query words: 0-7356-2405-4 978-0-7356-2405-4

Keywords: KB943829

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.