When you upgrade a SQL Server 2005 package, Integration Services migrates the scripts in any Script task and Script component to Microsoft Visual Studio Tools for Applications (VSTA). In SQL Server 2005, the scripts in Script tasks or Script components used Microsoft Visual Studio for Applications (VSA). For more information about changes that you might have to make to the scripts before migration and about script conversion failure, see Migrating Scripts to VSTA.

You can use various methods to upgrade SQL Server 2005 packages. For some of these methods, the upgrade is only temporary. For others, the upgrade is permanent. The following table describes each of these methods and whether the upgrade is temporary or permanent.

Upgrade Method

Type of Upgrade

Use the dtexec utility (dtexec.exe) that is installed with SQL Server 2008 to run a SQL Server 2005 package.

During the package upgrade process, most components and features in SQL Server 2005 packages convert seamlessly to their counterparts in SQL Server 2008. However, there are several component and features that either will not be upgraded or have upgrade results of which you should be aware. The following table identifies these components and features.

The names of certain providers have changed in SQL Server 2008 and require different values in the connection strings.

To update the connection strings, use one of the following procedures:

Use the SSIS Package Upgrade Wizard to upgrade the package, and select the Update connection strings to use new provider names option.

In Business Intelligence Development Studio, on the General page of the Options dialog box, select the Update connection strings to use new provider names option. For more information about this option, see General Page.

In Business Intelligence Development Studio, open the package and manually change the text of the ConnectionString property.

Note

You cannot use the previous procedures to update a connection string when the connection string is stored in either a configuration file or a data source file, or when an expression sets the ConnectionString property. To update the connection string in these cases, you must manually update the file or the expression.For more information about data sources, see Using Data Sources in Packages.

Lookup transformation

The package upgrade process automatically upgrades the Lookup transformation to the SQL Server 2008 version. However, the SQL Server 2008 version of this component has some additional capabilities of which you might want to take advantage.