You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article describes changes in feature availability and behavior between the current release and the previous release.
28
+
29
+
## Deprecated features
30
+
A *deprecated feature* will be discontinued from the product in a future release, but is still supported and included in the current release to maintain backward compatibility. It's recommended you discontinue using deprecated features in new and existing projects to maintain compatibility with future releases.
31
+
32
+
The following features are deprecated in this release:
33
+
34
+
|||
35
+
|-|-|
36
+
|**Mode/Category**|**Feature**|
37
+
|Tabular|Remote linked measure groups|
38
+
|Tabular|Models at the 1100 and 1103 compatibility level|
39
+
|Tabular|Tabular Object Model properties: Column.TableDetailPosition, Column.IsDefaultLabel, Column.IsDefaultImage|
40
+
|Multidimensional|Data Mining|
41
+
42
+
## Discontinued features
43
+
A *discontinued feature* was deprecated in an earlier release. It may continue to be included in the current release, but is no longer supported. Discontinued features may be removed entirely in a future release or update.
44
+
45
+
The following features were deprecated in an earlier release and are no longer supported in this release.
46
+
47
+
|||
48
+
|-|-|
49
+
|**Mode/Category**|**Feature**|
50
+
|Tabular|VertipaqPagingPolicy memory property value (2), enable paging to disk using memory mapped files.|
51
+
|Multidimensional|Remote partitions|
52
+
|Multidimensional|Remote linked measure groups|
53
+
|Multidimensional|Dimensional writeback|
54
+
|Multidimensional|Linked dimensions|
55
+
|Tools|SQL Server Profiler for Trace Capture<br /><br /> The replacement is to use Extended Events Profiler embedded in SQL Server Management Studio. <br /> See [Monitor Analysis Services with SQL Server Extended Events](../analysis-services/instances/monitor-analysis-services-with-sql-server-extended-events.md).|
56
+
|Tools|Server Profiler for Trace Replay <br />Replacement. There is no replacement.|
57
+
|Trace Management Objects and Trace APIs|Microsoft.AnalysisServices.Trace objects (contains the APIs for Analysis Services Trace and Replay objects). The replacement is multi-part:<br /><br /> - Trace Configuration: Microsoft.SqlServer.Management.XEvent<br />- Trace Reading: Microsoft.SqlServer.XEvent.Linq<br />- Trace Replay: None|
58
+
59
+
## Breaking changes
60
+
A *breaking change* causes a feature, data model, application code, or script to no longer function after upgrading to the current release.
61
+
62
+
There are no breaking changes in this release.
63
+
64
+
## Behavior changes
65
+
A *behavior change* affects how the same feature works in the current release as compared to the previous release. Only significant behavior changes are described. Changes in user interface are not included.
66
+
67
+
There are no behavior changes in this release.
68
+
69
+
70
+
## See also
71
+
[Analysis Services backward compatibility (SQL Server 2016)](analysis-services-backward-compatibility.md)
The topics in this section describe the changes in behavior between versions of [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)][!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)].
30
+
This article describes changes in feature availability and behavior between the current version and the previous version.
31
+
32
+
## Deprecated features
33
+
A *deprecated feature* will be discontinued from the product in a future release, but is still supported and included in the current release to maintain backward compatibility. It's recommended you discontinue using deprecated features in new and existing projects to maintain compatibility with future releases.
34
+
35
+
The following features are deprecated in this release:
36
+
37
+
|||
38
+
|-|-|
39
+
|**Mode/Category**|**Feature**|
40
+
|Multidimensional|Remote partitions|
41
+
|Multidimensional|Remote linked measure groups|
42
+
|Multidimensional|Dimensional writeback|
43
+
|Multidimensional|Linked dimensions|
44
+
|Multidimensional|SQL Server table notifications for proactive caching. <br />The replacement is to use polling for proactive caching. <br />See [Proactive Caching (Dimensions)](../analysis-services/multidimensional-models-olap-logical-dimension-objects/proactive-caching-dimensions.md) and [Proactive Caching (Partitions)](../analysis-services/multidimensional-models-olap-logical-cube-objects/partitions-proactive-caching.md).|
45
+
|Multidimensional|Session cubes. There is no replacement.|
46
+
|Multidimensional|Local cubes. There is no replacement.|
47
+
|Tabular|Tabular model 1100 and 1103 compatibility levels will not be supported in a future release. The replacement is to set models at compatibility level 1200 or higher, converting model definitions to tabular metadata. See [Compatibility Level for Tabular models in Analysis Services](../analysis-services/tabular-models/compatibility-level-for-tabular-models-in-analysis-services.md).|
48
+
|Tools|SQL Server Profiler for Trace Capture<br /><br /> The replacement is to use Extended Events Profiler embedded in SQL Server Management Studio. <br /> See [Monitor Analysis Services with SQL Server Extended Events](../analysis-services/instances/monitor-analysis-services-with-sql-server-extended-events.md).|
49
+
|Tools|Server Profiler for Trace Replay <br />Replacement. There is no replacement.|
50
+
|Trace Management Objects and Trace APIs|Microsoft.AnalysisServices.Trace objects (contains the APIs for Analysis Services Trace and Replay objects). The replacement is multi-part:<br /><br /> - Trace Configuration: Microsoft.SqlServer.Management.XEvent<br />- Trace Reading: Microsoft.SqlServer.XEvent.Linq<br />- Trace Replay: None|
51
+
52
+
> [!NOTE]
53
+
> Previously deprecated feature announcements from [!INCLUDE[ssSQL14](../includes/sssql14-md.md)] remain in effect. Because the code supporting those features has not yet been cut from the product, many of these features are still present in this release. While previously deprecated features might be accessible, they are still considered deprecated and could be physically removed from the product at any time.
54
+
55
+
## Discontinued features
56
+
A *discontinued feature* was deprecated in an earlier release. It may continue to be included in the current release, but is no longer supported. Discontinued features may be removed entirely in a future release or update.
57
+
58
+
The following features were deprecated in an earlier release and are no longer supported in this release.
59
+
60
+
|||
61
+
|-|-|
62
+
|**Feature**|**Replacment or workaround**|
63
+
|[CalculationPassValue (MDX)](../mdx/calculationpassvalue-mdx.md)|None. This feature was deprecated in SQL Server 2005.|
64
+
|[CalculationCurrentPass (MDX)](../mdx/calculationcurrentpass-mdx.md)|None. This feature was deprecated in SQL Server 2005.|
65
+
|NON_EMPTY_BEHAVIOR query optimizer hint|None. This feature was deprecated in SQL Server 2008.|
66
+
|COM assemblies|None. This feature was deprecated in SQL Server 2008.|
67
+
|CELL_EVALUATION_LIST intrinsic cell property|None. This feature was deprecated in SQL Server 2005.|
68
+
69
+
> [!NOTE]
70
+
> Previously deprecated feature announcements from [!INCLUDE[ssSQL14](../includes/sssql14-md.md)] remain in effect. Because the code supporting those features has not yet been cut from the product, many of these features are still present in this release. While previously deprecated features might be accessible, they are still considered deprecated and could be physically removed from the product at any time.
71
+
72
+
## Breaking changes
73
+
A *breaking change* causes a data model, application code, or script to no longer function after upgrading either the model or the server.
74
+
75
+
### .NET 4.0 version upgrade
76
+
Analysis Services Management Objects (AMO), ADOMD.NET, and Tabular Object Model (TOM) client libraries 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.
77
+
78
+
### AMO version upgrade
79
+
This release is a version upgrade for [Analysis Services Management Objects (AMO)](https://msdn.microsoft.com/library/mt436122.aspx) 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 instance, you must add the following namespace to make your code or script operational:
80
+
81
+
```
82
+
83
+
using Microsoft.AnalysisServices;
84
+
using Microsoft.AnalysisServices.Core;
85
+
86
+
```
31
87
32
-
## In This Section
88
+
The [Microsoft.AnalysisServices.Core](https://msdn.microsoft.com/library/microsoft.analysisservices.core.aspx) 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.
33
89
34
-
|Topics|Description|
35
-
|------------|-----------------|
36
-
|[Deprecated Analysis Services Features in SQL Server 2016](../analysis-services/deprecated-analysis-services-features-in-sql-server-2016.md)|Describes features that are retained in the current version to maintain backward compatibility, but which will be removed in a future version of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)].|
37
-
|[Discontinued Analysis Services Functionality in SQL Server 2016](../analysis-services/discontinued-analysis-services-functionality-in-sql-server-2016.md)|Describes features that existed in earlier versions of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] but are now officially unsupported in the current version.|
38
-
|[Breaking Changes to Analysis Services Features in SQL Server 2016](../analysis-services/breaking-changes-to-analysis-services-features-in-sql-server-2016.md)|Describes code changes introduced in this release of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] that could potentially break a model or custom applications or script created in previous versions of the software.|
39
-
|[Behavior Changes to Analysis Services Features in SQL Server 2016](../analysis-services/behavior-changes-to-analysis-services-features-in-sql-server-2016.md)|Describes existing features that have different behaviors in this release of [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)]. Common examples include changing a default to a new or different value, disallowing a previously allowable operation or configuration, or a introducing a requirement to manually revise or replace a setting or configuration that is lost during upgrade.|
90
+
Although there are now multiple namespaces, both exist in the same assembly (Microsoft.AnalysisServices.dll).
40
91
41
-
## See Also
42
-
[What's New in Analysis Services](../analysis-services/what-s-new-in-analysis-services.md)
To better support XEvent DISCOVER streaming in SSMS for SQL Server 2016 Analysis Services, `DISCOVER_XEVENT_TRACE_DEFINITION` is replaced with the following XEvent traces:
44
94
45
-
95
+
- DISCOVER_XEVENT_PACKAGES
96
+
97
+
- DISCOVER_XEVENT_OBJECT
98
+
99
+
- DISCOVER_XEVENT_OBJECT_COLUMNS
100
+
101
+
- DISCOVER_XEVENT_SESSION_TARGETS
102
+
103
+
## Behavior changes
104
+
A *behavior change* affects how features work or interact in the current version as compared to earlier versions of SQL Server.
105
+
106
+
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.
107
+
108
+
Feature behaviors that changed in this release, yet do not break an existing model or code post-upgrade, are listed here.
109
+
110
+
### Analysis Services in SharePoint mode
111
+
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 Analysis Services.
112
+
113
+
### DirectQuery mode for Tabular models
114
+
*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.
115
+
116
+
DirectQuery has existed as a data access mode for the last several releases. In SQL Server 2016 Analysis Services, the implementation has been slightly revised, assuming the tabular model is at compatibility level 1200 or higher. DirectQuery has fewer restrictions than before. It also has different database properties.
117
+
118
+
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 or higher to benefit from enhancements made to DirectQuery.
119
+
120
+
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 and higher compatibility levels. 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 or higher, and then reconfigure the DirectQuery properties. See [DirectQuery Mode](../analysis-services/tabular-models/directquery-mode-ssas-tabular.md) for details.
121
+
122
+
123
+
## See also
124
+
[Analysis Services backward compatibility (SQL Server 2017)](analysis-services-backward-compatibility-sql2017.md)
0 commit comments