Behavior Changes in Analysis Services
Collapse the table of content
Expand the table of content

Behavior Changes to Analysis Services Features in SQL Server 2016

 

Applies To: SQL Server 2016

A behavior change affects how features work or interact in the current version as compared to earlier versions of SQL Server.

Revisions to default values, manual configuration required to complete an upgrade or restore functionality, or a new implementation of an existing feature are all examples of a behavior change in the product.

Feature behaviors that changed in this release, yet do not break an existing model or code post-upgrade, are listed here.

System_CAPS_ICON_note.jpg Note


In contrast with a behavior change, a breaking change is one that prevents a data model or application integrated with Analysis Services from running after upgrading a server, client tool, or model. To see the list, visit Breaking Changes to Analysis Services Features in SQL Server 2016.

Running the Power Pivot Configuration wizard is no longer required as a post-installation task. This is true for all supported versions of SharePoint that load models from the current SQL Server 2016 release of Analysis Services.

DirectQuery is a data access mode for tabular models, where query execution is performed on a backend relational database, retrieving a result set in real time. It's often used for very large datasets that cannot fit in memory or when data is volatile and you want the most recent data returned in queries against a tabular model.

DirectQuery has existed as a data access mode for the last several releases. In SQL Server 2016, the implementation has been slightly revised, assuming the tabular model is at compatibility level 1200. DirectQuery has fewer restrictions than before. It also has different database properties.

If you are using DirectQuery in an existing tabular model, you can keep the model at its currently compatibility level of 1100 or 1103 and continue to use DirectQuery as its implemented for those levels. Alternatively, you can upgrade to 1200 to benefit from enhancements made to DirectQuery in this release of Analysis Services.

There is no in-place upgrade of a DirectQuery model because the settings from older compatibility levels do not have exact counterparts in the newer 1200 compatibility level. If you have an existing tabular model that runs in DirectQuery mode, you should open the model in SQL Server Data Tools, turn DirectQuery off, set the Compatibility Level property to 1200, and then reconfigure the DirectQuery properties as defined for tabular 1200 models. See DirectQuery Mode (SSAS Tabular) for details.

Backward Compatibility_deleted
Breaking Changes to Analysis Services Features in SQL Server 2016
Compatibility Level for Tabular models in Analysis Services
Download SQL Server Data Tools

Community Additions

ADD
Show:
© 2016 Microsoft