Interoperability and Coexistence (Integration Services)

SQL Server 2012 Integration Services (SSIS) can coexist side-by-side with SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS)

Features and Differences

The following table lists some of the differences between the current and earlier versions of Integration Services.

For additional information about the changes that occur when you upgrade SQL Server 2005 Integration Services (SSIS) or SQL Server 2008 Integration Services (SSIS) to SQL Server 2012 Integration Services (SSIS), see Upgrade Integration Services.

Side-by-Side Compatibility Issues

When you have SQL Server 2012 Integration Services (SSIS) installed side-by-side with SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS), you can perform the following tasks:

• Design packages in SQL Server Data Tools. You use the following tools to develop and maintain packages based on corresponding versions of SQL Server.

  • Use the SQL Server 2005 version of Business Intelligence Development Studio to develop and maintain packages that are based on SQL Server 2005 Integration Services (SSIS).

  • Use the SQL Server 2008 version of Business Intelligence Development Studio to develop and maintain packages that are based on SQL Server 2008 Integration Services (SSIS)

  • Use SQL Server Data Tools - Business Intelligence for Visual Studio 2012 to develop and maintain packages that are based on SQL Server 2012 Integration Services (SSIS). You can download it from here.

• Load and run packages. You can load and run packages that were developed in SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS), in the SQL Server 2012 version of SQL Server Data Tools (SSDT). When you add the package to an existing project, the package is permanently upgraded to the format that SQL Server 2012 Integration Services (SSIS) uses. When you open the package file in SQL Server Data Tools (SSDT), the package is temporarily upgraded to the format that SQL Server 2012 Integration Services (SSIS) uses. If you save the change to the package, the package is permanently upgraded. Once saved in the format that SQL Server 2012 Integration Services (SSIS) uses, packages can no longer be opened in the corresponding SQL Server 2005 or SQL Server 2008 version of Business Intelligence Development Studio, nor run by the corresponding SQL Server 2005 Integration Services (SSIS) or SQL Server 2008 Integration Services (SSIS) tools.

• Manage packages in SQL Server Management Studio. You cannot connect to an instance of the SQL Server 2012 version of the Integration Services service, from the SQL Server 2005 or the SQL Server 2008 version of Management Studio. You cannot connect to an instance of the SQL Server 2005 or the SQL Server 2008 version of the Integration Services service from the SQL Server 2012 version of Management Studio. You can use the SQL Server 2012 version of Management Studio to manage Integration Services packages that are stored in an instance of SQL Server 2008 or SQL Server 2012. You need to modify the service configuration file to add the instance of SQL Server 2008 to the list of locations managed by the service. For more information, see Configuring the Integration Services Service (SSIS Service).

• Store packages in SQL Server. You can store packages in the following databases.

  Package format	Database
  SQL Server 2005 Integration Services (SSIS)	msdb database of an instance of SQL Server 2005
  SQL Server 2008 Integration Services (SSIS)	msdb database of an instance of SQL Server 2008
  SQL Server 2012 Integration Services (SSIS)	msdb database of an instance of SQL Server 2012

  On an instance of SQL Server 2012, you can import packages from an instance of SQL Server 2005 or from an instance of SQL Server 2008, but you cannot export packages to an instance of SQL Server 2005 or to an instance of SQL Server 2008.

  On an instance of SQL Server 2005 or an instance of SQL Server 2008, you cannot import packages from, nor export packages to, an instance of SQL Server 2012.

• Run packages. You can run SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS) packages by using the SQL Server 2012 version of the dtexec utility or of SQL Server Agent. Whenever a SQL Server 2012 Integration Services (SSIS) tool loads a package that was developed in SQL Server 2005 Integration Services (SSIS) or SQL Server 2008 Integration Services (SSIS), the tool temporarily converts, in memory, the package to the package format that SQL Server 2012 Integration Services (SSIS) uses. If the SQL Server 2005 Integration Services (SSIS) or SQL Server 2008 Integration Services (SSIS) package has issues that prevent a successful conversion, the SQL Server 2012 Integration Services (SSIS) tool cannot run the package until those issues are resolved. For more information, see Upgrade Integration Services Packages.