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

Breaking Changes to Analysis Services Features in SQL Server 2016

 

Applies To: SQL Server 2016

A breaking change causes a data model, application code, or script to no longer function after upgrading either the model or the server.

System_CAPS_ICON_note.jpg Note


In contrast, a behavior change is characterized as a code change that doesn't break a model or application, but does introduce a different behavior from a previous release. Examples of behavior changes might include changing a default value, or disallowing a configuration of properties or options that was previously allowed. To learn more about behavior changes in this release, see Behavior Changes to Analysis Services Features in SQL Server 2016.

Analysis Services Management Objects (AMO), ADOMD.NET, and Tabular Object Model (TOM) client libraries in SQL Server 2016 Analysis Services (SSAS) now target the .NET 4.0 runtime. This can be a breaking change for applications that target .NET 3.5. Applications using newer versions of these assemblies must now target .NET 4.0 or later.

SQL Server 2016 Analysis Services (SSAS) is a version upgrade for Analysis Services Management Objects (AMO) and is a breaking change under certain circumstances. Existing code and scripts that call into AMO will continue to run as before if you upgrade from a previous version. However, if you need to recompile your application and you are targeting a SQL Server 2016 Analysis Services (SSAS) instance, you must add the following namespace to make your code or script operational:

  
using Microsoft.AnalysisServices;  
using Microsoft.AnalysisServices.Core;  
  

The Microsoft.AnalysisServices.Core namespace is now required whenever you reference the Microsoft.AnalysisServices assembly in your code. Objects that were previously only in the Microsoft.AnalysisServices namespace are moved to the Core namespace in this release if the object is used the same way in both tabular and multidimensional scenarios. For example, server-related APIs are relocated to the Core namespace.

Although there are now multiple namespaces, both exist in the same assembly (Microsoft.AnalysisServices.dll).

To better support XEvent DISCOVER streaming in SSMS for SQL Server 2016, DISCOVER_XEVENT_TRACE_DEFINITION is replaced with the following XEvent traces:

  • DISCOVER_XEVENT_PACKAGES

  • DISCOVER_XEVENT_OBJECT

  • DISCOVER_XEVENT_OBJECT_COLUMNS

  • DISCOVER_XEVENT_SESSION_TARGETS

Analysis Services Backward Compatibility

Community Additions

ADD
Show:
© 2016 Microsoft