| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | helpviewer_keywords | ||
|---|---|---|---|---|---|---|---|---|---|---|---|
Installing Integration Services Versions Side by Side |
Installing Integration Services Versions Side by Side |
chugugrace |
chugu |
03/14/2017 |
sql |
integration-services |
conceptual |
intro-installation |
|
[!INCLUDEsqlserver-ssis]
You can install [!INCLUDEssSQL19] Integration Services (SSIS) side-by-side with earlier versions of SSIS. This topic describes some limitations of side-by-side installations.
To design and maintain packages that target SQL Server 2016, SQL Server 2014, or SQL Server 2012, use SQL Server Data Tools (SSDT) for Visual Studio 2015. To get SSDT, see Download Latest SQL Server Data Tools.
In the property pages for an Integration Services project, on the General tab of Configuration Properties, select the TargetServerVersion property and choose SQL Server 2016, SQL Server 2014, or SQL Server 2012.
| Target version of SQL Server | Development environment for SSIS packages |
|---|---|
| 2016 | SQL Server Data Tools for Visual Studio 2015 |
| 2014 | SQL Server Data Tools for Visual Studio 2015 or SQL Server Data Tools - Business Intelligence for Visual Studio 2013 |
| 2012 | SQL Server Data Tools for Visual Studio 2015 or SQL Server Data Tools - Business Intelligence for Visual Studio 2012 |
| 2008 | Business Intelligence Development Studio from SQL Server 2008 |
When you add an existing package to an existing project, the package is converted to the format targeted by the project .
You can use the [!INCLUDEssSQL19] version of the dtexec utility or of [!INCLUDEssNoVersion] Agent to run Integration Services packages created by earlier versions of the development tools. When these [!INCLUDEssSQL19] tools load a package that was developed in an earlier version of the development tools, the tool temporarily converts the package in memory to the package format that [!INCLUDEssISCurrent] uses. If the package has issues that prevent a successful conversion, the [!INCLUDEssSQL19] tool can't run the package until those issues are resolved. For more info, see Upgrade Integration Services Packages.