Applies To: SQL Server 2016
When you upgrade an instance of SQL Server 2008 to the current release of SQL Server, your existing SQL Server 2008 Integration Services (SSIS) packages are not automatically upgraded to the package format that the current release SQL ServerIntegration Services uses. You will have to select an upgrade method and manually upgrade your packages.
For information on upgrading packages when you convert a project to the project deployment model, see Deploy Projects to Integration Services Server.
You can use various methods to upgrade SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 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 the current release of SQL Server to run a SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 package.|
For more information, see dtexec Utility.
|The package upgrade is temporary.|
The changes cannot be saved.
|Open a SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 package file in SQL Server Data Tools (SSDT).||The package upgrade is permanent if you save the package; otherwise, it is temporary if you do not save the package.|
|Add a SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 package to an existing project in SQL Server Data Tools (SSDT).||The package upgrade is permanent.|
|Open a SQL Server 2008 Integration Services (SSIS) or later project file in Visual Studio, and then use the SSIS Package Upgrade Wizard to upgrade multiple packages in the project.|
For more information, see Upgrade Integration Services Packages Using the SSIS Package Upgrade Wizard and SSIS Package Upgrade Wizard F1 Help.
|The package upgrade is permanent.|
|Use the Upgrade method to upgrade one or more Integration Services packages.||The package upgrade is permanent.|
SQL Server 2005 Integration Services (SSIS) custom components will not work with the current release of SQL ServerIntegration Services.
You can use the current release of SQL ServerIntegration Services tools to run and manage packages that include SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014SSIS custom components. We added four binding redirection rules to the following files to help redirect the runtime assemblies from version 10.0.0.0 (SQL Server 2008 R2), version 188.8.131.52 (SQL Server 2012), or version 184.108.40.206 (SQL Server 2014) to version 220.127.116.11 (SQL Server 2016).
To use SQL Server Data Tools to design packages that include SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 custom components, you need to modify the devenv.exe.config file that is located at <drive>:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE.
To use these packages with customer applications that are built with the runtime for SQL Server 2016, include redirection rules in the configuration section of the *.exe.config file for the executable. The rules redirect the runtime assemblies to version 18.104.22.168 (SQL Server 2016). For more information about assembly version redirection, see <assemblyBinding> Element for <runtime>.
In SQL Server 2016, the Integration Services assemblies were upgraded to .NET 4.0. There is a separate global assembly cache for .NET 4, located in <drive>:\Windows\Microsoft.NET\assembly. You can find all of the Integration Services assemblies under this path, usually in the GAC_MSIL folder.
As in previous versions of SQL Server, the core Integration Services extensibility .dll files are also located at <drive>:\Program Files\Microsoft SQL Server\130\SDK\Assemblies.
During the package upgrade process, most components and features in SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 packages convert seamlessly to their counterparts in the current release of SQL Server. However, there are several components 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.
|Component or Feature||Upgrade Results|
|Connection strings||For SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014 packages, the names of certain providers have changed 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 SQL Server Data Tools (SSDT), 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 SQL Server Data Tools (SSDT), 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 Data Sources.
Script Task and Script Component scripts that explicitly reference ADODB.dll may not upgrade or run on machines without SQL Server Management Studio or SQL Server Data Tools (SSDT) installed. In order to upgrade these Script Task or Script Component scripts, it is recommended that you remove the dependency on ADODB.dll. Ado.Net is the recommended alternative for managed code such as VB and C# scripts.