598 Hands-On Microsoft SQL Server 2008 Integration Services 5. Type or select an Instance Name from the drop-down list box in the Connection Parameters screen. Specify the authentication details for the selected instance and click Next when ready. Don’t get confused between versions of SQL Server. The Upgrade Advisor connects to SQL Server 2000 to analyze and report, so specify an instance of SQL Server 2000 here. 6. On the DTS Parameters screen, you can select whether you want to analyze DTS 2000 packages that are saved in the SQL Server or the packages saved on the file system. Select the Analyze DTS Package Files radio button and then type C:\SSIS\RawFiles in the Path To DTS Packages field. Click Next to move on. 7. Review the settings in the Confirm Upgrade Advisor Settings screen. Click Run to analyze the selected package. 8. In the next screen, the Upgrade Advisor will analyze the package; when it completes analysis, you can see the report by clicking Launch Report. The Figure 14-1 Starting installation of the Upgrade Advisor Chapter 14: Migrating to Integration Services 2008 599 analysis report will be displayed in the Upgrade Advisor Report Viewer. The key messages that you can spot in the report among other messages are at you need to install SQL Server 2000 DTS Designer Components to edit c the packages in Integration Services. Packages stored in Meta Data Services are not supported. c SQL Server 2000 Data Transformation Services has been deprecated. c Review Depending on the complexity and the components used in the package, you will see different messages for your packages. But you will find that the previously mentioned three key messages are common to all types of packages, as these are generic messages representing major differences between DTS and SSIS. Figure 14-2 Selecting Data Transformation Services for analysis 600 Hands-On Microsoft SQL Server 2008 Integration Services Migrating Data Transformation Services Packages In this part of the chapter you will study the options available to you to migrate your existing DTS 2000 packages to Integration Services 2008. You will work with a test package that has been developed in Data Transformation Services (DTS) and will understand the requirements of different methods and the end results achieved that can affect your choice of the option. But first of all, let’s start with the options you have for DTS 2000 packages. Migration Options After having run Upgrade Advisor for DTS packages, you can view the report that will tell you whether your package can or cannot be upgraded, given the complexity and the components used in the package. At that time, you need to consider the options available for the DTS 2000 packages that are still in use. Some preconditions will affect the option you choose. While considering crossing the migration bridge, one thing you need always to bear in mind is that Integration Services is new software that has been developed from the ground up. Though it has adopted most of the DTS 2000 concepts, it is totally different in usability and operation; above all, not all DTS 2000 tasks are available in Integration Services. Some of them have been deprecated, and some have been removed. But the good news is that Integration Services can coexist with DTS and also provides necessary tools for you to migrate. You also need to be aware of the fact that not all versions of SQL Server 2008 include Integration Services. SQL Server 2008 Standard Edition has basic Integration Services transformations, whereas the Developer, Enterprise, and Datacenter Editions have advanced transformations built into them. The remaining versions (Express, Workgroup, and Web Editions) do not have Integration Services, though the Express Edition has an Import and Export Wizard utility (still, it is not the Integration Services service). While discussing your options, we will focus only on the editions that have Integration Services built into them. Another consideration is the storage location of your package. You were able to store your DTS 2000 packages in SQL Server, Structured Storage File, or in Meta Data services, also known as the repository. Integration Services can access DTS 2000 packages that were saved in SQL Server 2000 or Structured Storage File for executing or migrating, but Integration Services does not support Meta Data services. If you have DTS 2000 packages saved to Meta Data services, you can export the packages from Meta Data services to SQL Server or Structured Storage File for Integration Services easy Chapter 14: Migrating to Integration Services 2008 601 access. However, if you cannot do this, you will have to install SQL Server 2000, SQL Server 2000 tools, or repository redistributable files on your local computer to enable Integration Services to scan and migrate the packages saved in Meta Data services. At the time of upgrading your database server, you might have to migrate all your packages and test them on the SSIS environment before you can commission an SQL Server 2008 migration project. This alone can be a deterrent to the upgrade project and can cause long delays. The following options are available while moving to Integration Services: Running DTS 2000 packages as-is with run-time support c Embedding DTS 2000 packages in Integration Services packages using a wrapper c task Migrating DTS 2000 packages to Integration Services using the Package c Migration Wizard Installing DTS 2000 Support Components Before we get into exploring the options available for handling DTS 2000 packages, let’s install the components you will require to work with legacy packages. You can install DTS 2000 run-time and design-time support components on 32-bit systems, whereas 64-bit systems have limited support. There is no 64-bit design-time or run- time support for DTS packages. However, if you install the 32-bit version of dtexec utility, you can run DTS 2000 packages in 32-bit mode on a 64-bit computer. On Itanium-based operating systems, however, you cannot even do that, as there is no support for DTS packages. Hence you cannot create, view, modify, or run DTS packages on Itanium-based operating systems. If you need to modify DTS 2000 packages, you should be using 32-bit systems. The details and exercises covered in this chapter refer to 32-bit systems. You need to install multiple components to provide support to DTS 2000 packages in Integration Service. The following are the steps involved in installing a complete support for Data Transformation Packages: Basic Installation c When you choose Integration Services in the Feature Selection page during installation, the ActiveX Script task and the DTS Package Migration Wizard are installed. As this has been already installed in our test environment, you don’t need to do anything for this step. ActiveX task is really provided to support existing scripts that have been developed in DTS. You should not develop new scripts using this task, as it is marked deprecated and will be removed in future releases. 602 Hands-On Microsoft SQL Server 2008 Integration Services Clients Tools Backwards Compatibility c When you choose Clients Tools Backwards Compatibility feature in the Feature Selection page during installation, Execute DTS 2000 Package task is installed. However, you also need to install the DTS run time in order to use this component. Run SQL Server 2008 installation and choose the Client Tools Backwards Compatibility feature in the Feature Selection page as shown in Figure 14-3. DTS run time c To install DTS run-time support, search for the sqlserver2005_ bc.msi file in the SQL Server installation media. On the media I’m using, the file exists under 1033_enu_lp\x86\setup\x86 folder. Double-click this file to install SQL Server 2005 Backward Compatibility software, which also installs the DTS run-time engine (refer to Figure 14-4). Complete the installation wizard. DTS Designer Components c SQL Server 2000 DTS Designer Components allow you to edit and maintain DTS 2000 packages until they can be migrated to Integration Services. Download SQL Server 2000 DTS Designer Components Figure 14-3 Installing the Client Tools Backwards Compatibility feature Chapter 14: Migrating to Integration Services 2008 603 from the Microsoft Download Center. is software has been released with the SQL Server 2005 Feature pack. From the Feature Pack for SQL Server 2005 page, locate the Microsoft SQL Server 2000 DTS Designer Components section and download the SQLServer2005_DTS.msi file. Once the download is complete, double-click the SQLServer2005_DTS.msi file to start the installation wizard (see Figure 14-5) for DTS Designer Components. Click Next on the Welcome screen. Installation is straightforward. Go ahead and complete the installation. It is worth mentioning couple of issues with these legacy software components. As various versions of SQL Server and the underlying operating systems have been released, the components also needed to be revised time to time, though they are still released with the SQL Server 2005 feature pack. You need to install the latest version available at the time. I’ve used the ones released in December 2008 that have worked on Windows 2008 with SQL Server 2008 R2. Earlier versions didn’t work with Windows 2008 due to Data Execution Prevention (DEP) technology. Both the latest run time and the designer components have been included in the code files of this chapter. Another issue was observed during installation the path to the sqlgui.dll library. For DTS you need to use the legacy file that resides in C:\Program Files\Microsoft SQL Server\80\Tools Binn\ and not the one that resides in C:\Program Files\Microsoft Figure 14-4 Installing Data Transformation Services 2000 run time 604 Hands-On Microsoft SQL Server 2008 Integration Services SQL Server\100\Tools Binn\. To avoid using new sqlgui.dll, you need to modify the path system variable in the advanced properties of the computer and move the former listed path before the later in the path variable value. After installation of these components, you are now ready to explore the earlier discussed options in detail and see how well they fit with your scenario. Running DTS 2000 Packages As-Is with Run-Time Support If you are busy dealing with other stuff while migrating to SQL Server 2008, you may want to leave your DTS packages running as is and focus on migration later. You can run the DTS 2000 run-time environment and Integration Services on the same computer. However, some of the databases to which DTS 2000 package connects might get upgraded to SQL Server 2008, leaving DTS 2000 unable to access them. To deal with this issue, the run-time software has been enhanced to an updated version of the DTS 2000 run-time environment that is capable of accessing SQL Server 2005/2008 databases. In the following Hands-On exercise, you will discover how you can manage DTS 2000 packages in SQL Server 2008. Figure 14-5 Installation Wizard for SQL Server 2000 DTS Designer Components Chapter 14: Migrating to Integration Services 2008 605 Hands-On: Executing a DTS 2000 Package The scenario is that you have upgraded your SQL Server 2000 instance to SQL Server 2008 and have installed Integration Services and the DTS 2000 run time. Here you will learn how you can manage and run DTS 2000 packages. Method A DTS 2000 package, Importing Contacts, is available in a C:\SSIS\RawFiles folder saved in a structured storage file. This package imports records from the C:\SSIS\ RawFiles\Contacts.txt flat file to the Contacts table of the Campaign database. Contacts.txt is a fixed-width file, and the Importing Contacts package uses a flat file source, an OLE DB provider for SQL Server, and a Transform Data task to import data into SQL Server. Starting with a structured storage file, you will investigate how the package can be managed and modified in SQL Server Management Studio based on the various storage locations. The steps involved are as follows: Enumerate and import the package to SQL Server using SQL Server c Management Studio. Export and execute the DTS 2000 package. c Exercise (Enumerate and Import the DTS 2000 Package in SQL Server Management Studio) When you save DTS 2000 packages to SQL Server 2000, you know they are saved to the sysdtspackages table of the MSDB database. These packages are visible in the Local Packages node under Data Transformation Services in Enterprise Manager. In this part, you will explore how SQL Server Management Studio enumerates legacy packages. 1. Start SQL Server Management Studio and connect to the local SQL Server 2008 database engine. 2. In the Object Explorer window, expand Management | Legacy | Data Transformation Services. Your legacy packages—i.e., DTS 2000 packages— will show up under this node. 3. Right-click the Data Transformation Services and choose Import Package File from the context menu, as shown in Figure 14-6. In the Import DTS 2000 Package dialog box, choose Importing Contacts.dts Package from C:\SSIS\RawFiles and click Open. 606 Hands-On Microsoft SQL Server 2008 Integration Services 4. Because a structured storage file can have more than one package and package version, you are asked to choose the package you want to import in the Select Package dialog box. Expand the Importing Contacts package and choose any of the versions; then click OK to select your package. These packages are the same, just saved a few seconds apart. 5. Go back to Data Transformation Services node to see that the Importing Contacts package has been added there. 6. Click New Query and run the following query in the New Query tab: SELECT * FROM msdb.dbo.sysdtspackages You will see the Importing Contacts package listed in the output results along with any other packages that you might have in sysdtspackages table. This means that all the DTS 2000 packages are still saved in the msdb.dbo.sysdtspackages table and can be added to this table using the import facility provided by SQL Server Management Studio. You can enumerate DTS 2000 packages with SQL Server Management Studio and import and export DTS 2000 packages from the sysdtspackages table. However, if you need to modify the DTS 2000 packages, you must have SQL Server 2000 tools on the computer or take them away to a computer where SQL Figure 14-6 Importing a DTS 2000 package in SQL Server Management Studio Chapter 14: Migrating to Integration Services 2008 607 Server 2000 is installed. This is not a very helpful situation. To overcome such issues, Microsoft has provided SQL Server 2000 DTS Designer Components so that you can modify DTS 2000 packages from SQL Server Management Studio. You have already installed these components earlier; however, if you have skipped that step, then this is the time to install them. Exercise (Edit and Execute a DTS 2000 Package) You will use the SQL Server 2000 DTS Designer components to edit the Importing Contacts package and then run the package. 7. In the SQL Server Management Studio, go to the Data Transformation Services node and right-click the Importing Contacts package. Select Open from the context menu to open the Importing Contacts package in the DTS 2000 Package Designer, as shown in Figure 14-7. 8. In the DTS 2000 Package Designer, double-click the Campaign to open the Microsoft OLE DB Provider for SQL Server Connection Properties and provide the name of your server in the Server field or specify (local) to refer to the local server. The provided name SARTH is the name of computer used in setup lab for this book. Change it to your computer name. In the Database field, select Campaign (Figure 14-8). Click OK to close this dialog box. Do not select the check box in the Task References dialog box, and click OK to close it. Figure 14-7 The Importing Contacts package in the DTS 2000 Package Designer . Installing Data Transformation Services 2000 run time 604 Hands-On Microsoft SQL Server 2008 Integration Services SQL Server 100Tools Binn. To avoid using new sqlgui.dll, you need to modify. to Integration Services 2008 605 Hands-On: Executing a DTS 2000 Package The scenario is that you have upgraded your SQL Server 2000 instance to SQL Server 2008 and have installed Integration Services. Selecting Data Transformation Services for analysis 600 Hands-On Microsoft SQL Server 2008 Integration Services Migrating Data Transformation Services Packages In this part of the chapter you will