What's New in Integration Services
Applies To: SQL Server 2016 Preview
This topic describes the features that have been added or updated in SQL Server 2016 Integration Services .
Better package management
Expanded connectivity on premises
Expanded connectivity to the cloud
Azure Storage connectors and Hive and Pig tasks for HDInsight - Azure Feature Pack for SSIS released for SQL Server 2016
Usability and productivity
Better install experience
Better design experience
Multiple designer improvements and bug fixes.
(later) Designer support for multiple versions of SSIS.
Better SQL Server Management Studio experience
CTP 3.1 November 2015
CTP 3.0 October 2015
CTP 2.4 September 2015
CTP 2.3 August 2015
CTP 2.2 July 2015
[CTP 3.1] Most SSIS catalog views now perform better when they're run by a user who is not a member of the ssis_admin role.
[CTP 3.0] Save a commonly used control flow task or container to a standalone template file and reuse it multiple times in one or more packages in a project by using control flow templates. This reusability makes SSIS packages easier to design and maintain. For more info, see Reuse Control Flow across Packages by Using Control Flow Templates.
[CTP 3.0] When you set the value of the new AutoAdjustBufferSize property to true, the data flow engine automatically calculates the buffer size for the data flow. For more info, see Data Flow Performance Features.
[CTP 3.0] The Azure Feature Pack for Integration Services has been released for SQL Server 2016. The feature pack contains connection managers to connect to Azure data sources and tasks to do common Azure operations. For more info, see Azure Feature Pack.
[CTP 3.0] Support for HDFS contains connection managers to connect to Hadoop clusters and tasks to do common HDFS operations. For more info, see Hadoop and HDFS Support in Integration Services.
[CTP 3.0] The SQL Server Import and Export Wizard can now import data from, and save data to, Azure Blob Storage. For more info, see Choose a Data Source (SQL Server Import and Export Wizard) and Choose a Destination (SQL Server Import and Export Wizard).
[CTP 3.0] If the SSIS catalog database (SSISDB) belongs to an AlwaysOn Availability Group, you have to remove SSISDB from the availability group, upgrade SQL Server, then add SSISDB back to the availability group. For more info, see Upgrading SSISDB in an availability group.
[CTP 2.4] The Excel Connection Manager, the Excel Source and the Excel Destination, and the SQL Server Import and Export Wizard now support Excel 2013 data sources.
[CTP 2.4] The Balanced Data Distributor transformation, which required a separate download in previous versions of SQL Server, is now installed when you install Integration Services. For more info, see Balanced Data Distributor Transformation.
[CTP 2.4] The Data Feed Publishing Components, which required a separate download in previous versions of SQL Server, are now installed when you install Integration Services. For more info, see Data Streaming Destination.
[CTP 2.3] The Incremental Package Deployment feature lets you deploy one or more packages to an existing or new project without deploying the whole project. You can incrementally deploy packages by using the following tools.
SQL Server Management Studio (which uses the Deployment Wizard)
SQL Server Data Tools (Visual Studio) (which also uses the Deployment Wizard)
The Management Object Model (MOM) API
For more info, see Deploy Packages to Integration Services Server .
[CTP 2.3] When you upgrade SSIS projects from previous versions to the current version, the project-level connection managers continue to work as expected and the package layout and annotations are retained.
[CTP 2.3] The OData Source and the OData Connection Manager now support the OData v3 and v4 protocols.
For OData V3 protocol, the component supports the ATOM and JSON data formats .
For OData V4 protocol, the component supports the JSON data format .
For more info, see OData Source.
[CTP 2.3] When you redirect rows in the data flow that contain errors to an error output, the output contains a numeric identifier for the column in which the error occurred, but does not display the name of the column. There are now several ways to find or display the name of the column in which the error occurred.
In the Script Component or a custom data flow component, call the new GetIdentificationStringByLineage Id method of the IDTSComponentMetadata100 interface.
Select the DiagnosticEx event for logging when you configure logging. This event writes a data flow lineage map to the log. You can then look up the column name in this lineage map by using the column identifier captured by an error output. For more info, see Error Handling in Data.
In the Advanced Editor, you can see the column name for the upstream column when you view the properties of an input or output column of a data flow component.
To see the names of the columns in which the error occurred, attach a Data Viewer to an error output. The Data Viewer now displays both the description of the error and the name of the column in which the error occurred.
For more info about this improvement, see the following blog post by SSIS developer Bo Fan: Error Column Improvements for SSIS Data Flow.
[CTP 2.3] SSIS projects are now in SQL Server Data Tools. For more info, see Download Latest SQL Server Data Tools.
[CTP 2.3] Previous versions of the SSIS catalog let you choose from four built-in logging levels when you run a package: None, Basic, Performance, or Verbose. SQL Server 2016 adds the RuntimeLineage logging level. In addition, you can now create and save multiple customized logging levels in the SSIS catalog, and pick the logging level to use every time you run a package. For each customized logging level, select only the statistics and events you want to capture. Optionally include the event context to see variable values, connection strings, and task properties. For more info, see Enable Logging for Package Execution on the SSIS Server.
[CTP 2.3] The new RuntimeLineage logging level in the SSIS catalog collects the data required to track lineage in the data flow.
[CTP 2.3] In previous versions of the SSIS catalog, only users in the ssis_admin role can access the views that contain logging output. There is now a new ssis_logreader database-level role that you can use to grant permissions to access the views that contain logging output to users who aren't administrators.
There is also a new ssis_monitor role. This role supports AlwaysOn and is for internal use only by the SSIS catalog.
[CTP 2.2] The AlwaysOn Availability Groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. An availability group supports a failover environment for a discrete set of user databases known as availability databases that fail over together. For more information, see AlwaysOn Availability Groups.
In SQL Server 2016, SSIS introduces new capabilities that let you easily deploy to a centralized SSIS Catalog (i.e. SSISDB user database). In order to provide high availability for the SSISDB database and its contents - projects, packages, execution logs, and so on - you can add the SSISDB database to an AlwaysOn Availability Group, just like any other user database. When a failover occurs, one of the secondary nodes automatically becomes the new primary node.
For a detailed overview and step-by-step instructions for enabling AlwaysOn for SSISDB, see AlwaysOn for SSIS Catalog (SSISDB).