Export (0) Print
Expand All

What's New in Integration Services

 

Applies To: SQL Server 2016 Preview

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).

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.

  • Deployment Wizard

  • SQL Server Management Studio (which uses the Deployment Wizard)

  • SQL Server Data Tools (Visual Studio) (which also uses the Deployment Wizard)

  • Stored procedures

  • The Management Object Model (MOM) API

For more info, see Deploy Packages to Integration Services Server .

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.

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.

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.

The new RuntimeLineage logging level in the SSIS catalog collects the data required to track lineage in the data flow.

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.

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.

SSIS projects are now in SQL Server Data Tools. For more info, see Download Latest SQL Server Data Tools.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2015 Microsoft