Skip to content

Commit c4263df

Browse files
author
Owen Duncan
committed
Added Applies to banner
1 parent 1829732 commit c4263df

9 files changed

Lines changed: 81 additions & 58 deletions

‎docs/analysis-services/behavior-changes-to-analysis-services-features-in-sql-server-2016.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,9 @@ manager: "erikre"
3636

3737
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.
3838

39-
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 (SSAS Tabular)](../analysis-services/tabular-models/directquery-mode-ssas-tabular.md) for details.
39+
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.
4040

41-
## See Also
41+
## See also
4242
[Backward Compatibility_deleted](http://msdn.microsoft.com/library/15d9117e-e2fa-4985-99ea-66a117c1e9fd)
4343
[Breaking Changes to Analysis Services Features in SQL Server 2016](../analysis-services/breaking-changes-to-analysis-services-features-in-sql-server-2016.md)
4444
[Compatibility Level for Tabular models in Analysis Services](../analysis-services/tabular-models/compatibility-level-for-tabular-models-in-analysis-services.md)

‎docs/analysis-services/tabular-models/add-sample-data-to-a-directquery-model-in-design-mode.md‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Add sample data to a DirectQuery model in Design Mode | Microsoft Docs"
2+
title: "Add sample data to a DirectQuery model in Design Mode | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "03/01/2017"
4+
ms.date: "07/06/2017"
55
ms.prod: "sql-server-2016"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -15,7 +15,10 @@ author: "Minewiskan"
1515
ms.author: "owend"
1616
manager: "erikre"
1717
---
18-
# Add sample data to a DirectQuery model in Design Mode
18+
# Add sample data to a DirectQuery model in Design Mode
19+
20+
[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
21+
1922
In DirectQuery mode, table partitions are used to either create sample data subsets used during model design, or create alternatives of a full data view.
2023

2124
When you deploy a DirectQuery tabular model, only one partition is allowed per table, and that partition by necessity must be full data view. Any additional partition is either a substitute for a full data view or sample data. In this topic, we're going to describe creating a sample partition, with a subset of data.

‎docs/analysis-services/tabular-models/compatibility-level-for-tabular-models-in-analysis-services.md‎

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Compatibility Level for Tabular models in Analysis Services | Microsoft Docs"
2+
title: "Compatibility level for tabular models in Analysis Services | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "05/23/2017"
4+
ms.date: "07/06/2017"
55
ms.prod: "sql-server-2016"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -20,6 +20,8 @@ ms.author: "owend"
2020
manager: "erikre"
2121
---
2222
# Compatibility level for Analysis Services tabular models
23+
[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
24+
2325
The *compatibility level* refers to release-specific behaviors in the Analysis Services engine. For example, DirectQuery and tabular object metadata have different implementations depending on the compatibility level. In-general, you should choose the latest compatibility level supported by your servers.
2426

2527
**The latest compatibility level is 1400**
@@ -32,6 +34,7 @@ Major features in the 1400 compatibility level include:
3234
* Object-level security for table and column names, in addition to the data within them.
3335
* Enhanced support for ragged hierarchies.
3436
* Performance and monitoring improvements.
37+
3538

3639
## Supported compatibility levels by version
3740

@@ -45,7 +48,7 @@ Major features in the 1400 compatibility level include:
4548

4649

4750
## Set compatibility level
48-
When creating a new Tabular model project in SQL Server Data Tools (SSDT), you can specify the compatibility level on the **Tabular model designer** dialog.
51+
When creating a new tabular model project in SQL Server Data Tools (SSDT), you can specify the compatibility level on the **Tabular model designer** dialog.
4952

5053
![ssas_tabularproject_compat1200](../../analysis-services/tabular-models/media/ssas-tabularproject-compat1200.png)
5154

@@ -61,7 +64,7 @@ Major features in the 1400 compatibility level include:
6164

6265
This property specifies the highest compatibility level of a database that will run on the server. The supported compatibility level is read-only cannot be changed.
6366

64-
## See Also
67+
## See also
6568
[Compatibility Level of a multidimensional database](../../analysis-services/multidimensional-models/compatibility-level-of-a-multidimensional-database-analysis-services.md)
6669
[What's new in Analysis Services](../../analysis-services/what-s-new-in-analysis-services.md)
6770
[Create a new tabular model project](../../analysis-services/tabular-models/create-a-new-tabular-model-project-analysis-services.md)

‎docs/analysis-services/tabular-models/dax-formula-compatibility-in-directquery-mode-ssas-2016.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "DAX Formula Compatibility in DirectQuery Mode (SSAS 2016) | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "03/01/2017"
4+
ms.date: "07/06/2017"
55
ms.prod: "sql-server-2016"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -17,7 +17,9 @@ ms.author: "owend"
1717
manager: "erikre"
1818
---
1919
# DAX Formula Compatibility in DirectQuery Mode
20-
For tabular 1200 and higher models, many functional limitations in earlier versions no longer apply. For DAX formulas in-particular:
20+
[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
21+
22+
For tabular 1200 and higher models in DirectQuery mode, many functional limitations in earlier versions no longer apply. For DAX formulas in-particular:
2123

2224
- DirectQuery now generates simpler queries, providing improved performance.
2325
- Row level security (RLS) is now supported in DirectQuery mode.

‎docs/analysis-services/tabular-models/define-partitions-in-directquery-models-ssas-tabular.md‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Define partitions in DirectQuery models (SSAS Tabular) | Microsoft Docs"
33
ms.custom:
44
- "SQL2016_New_Updated"
5-
ms.date: "03/01/2017"
5+
ms.date: "07/06/2017"
66
ms.prod: "sql-server-2016"
77
ms.reviewer: ""
88
ms.suite: ""
@@ -16,7 +16,10 @@ author: "Minewiskan"
1616
ms.author: "owend"
1717
manager: "erikre"
1818
---
19-
# Define partitions in DirectQuery models (SSAS Tabular)
19+
# Define partitions in DirectQuery models
20+
21+
[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
22+
2023
This section explains how partitions are used in DirectQuery models. For more general information about partitions in tabular models, see [Partitions (SSAS Tabular)](../../analysis-services/tabular-models/partitions-ssas-tabular.md).
2124

2225
> [!NOTE]
@@ -74,7 +77,7 @@ manager: "erikre"
7477
|DataView=Sample<br /><br /> Applies to Tabular models using sample data views|Allow partition to be processed|If the model is using sample data, you can process the table to return a filtered dataset that provides visual cues during model design.|
7578
|DirectQueryUsage=InMemory With DirectQuery<br /><br /> Applies to Tabular 1100 or 1103 models running in a combination of in-memory and DirectQuery mode|Allow partition to be processed|If the model is using hybrid mode, you should use the same partition for queries against the in-memory and DirectQuery data source.|
7679

77-
## See Also
80+
## See also
7881
[Partitions &#40;SSAS Tabular&#41;](../../analysis-services/tabular-models/partitions-ssas-tabular.md)
7982

8083

‎docs/analysis-services/tabular-models/directquery-mode-ssas-tabular.md‎

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
2-
title: "DirectQuery Mode (SSAS Tabular) | Microsoft Docs"
2+
title: "DirectQuery Mode | Microsoft Docs"
33
ms.custom:
44
- "SQL2016_New_Updated"
5-
ms.date: "03/01/2017"
5+
ms.date: "07/06/2017"
66
ms.prod: "sql-server-2016"
77
ms.reviewer: ""
88
ms.suite: ""
@@ -18,7 +18,10 @@ author: "Minewiskan"
1818
ms.author: "owend"
1919
manager: "erikre"
2020
---
21-
# DirectQuery Mode (SSAS Tabular)
21+
# DirectQuery Mode
22+
23+
[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
24+
2225
This topic describes *DirectQuery mode* for Analysis Services tabular models at the 1200 and higher compatibility levels
2326
. DirectQuery mode can be turned on for models you're designing in SSDT, or for tabular models that have already been deployed, you can change to DirectQuery mode in SSMS. Before choosing DirectQuery mode, it's important to understand both the benefits and restrictions.
2427

@@ -31,7 +34,7 @@ manager: "erikre"
3134

3235
- Datasets can be larger than the memory capacity of an Analysis Services server.
3336

34-
- DirectQuery can take advantage of provider-side query acceleration, such as that provided by xVelocity memory optimized column indexes.
37+
- DirectQuery can take advantage of provider-side query acceleration, such as that provided by memory optimized column indexes.
3538

3639
- Security can be enforced by the back-end database , using row-level security features from the database (alternatively, you can use row-level security in the model via DAX).
3740

‎docs/analysis-services/tabular-models/enable-directquery-mode-in-ssdt.md‎

Lines changed: 23 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,25 @@
1-
---
2-
title: "Enable DirectQuery mode in SSDT | Microsoft Docs"
3-
ms.custom:
4-
- "SQL2016_New_Updated"
5-
ms.date: "03/01/2017"
6-
ms.prod: "sql-server-2016"
7-
ms.reviewer: ""
8-
ms.suite: ""
9-
ms.technology:
10-
- "analysis-services"
11-
ms.tgt_pltfrm: ""
12-
ms.topic: "article"
13-
ms.assetid: 71fc7ebd-2e86-4a76-994b-66d3a57bcc9b
14-
caps.latest.revision: 16
15-
author: "Minewiskan"
16-
ms.author: "owend"
17-
manager: "erikre"
18-
---
19-
# Enable DirectQuery mode in SSDT
1+
---
2+
title: "Enable DirectQuery mode in SSDT | Microsoft Docs"
3+
ms.custom:
4+
- "SQL2016_New_Updated"
5+
ms.date: "07/06/2017"
6+
ms.prod: "sql-server-2016"
7+
ms.reviewer: ""
8+
ms.suite: ""
9+
ms.technology:
10+
- "analysis-services"
11+
ms.tgt_pltfrm: ""
12+
ms.topic: "article"
13+
ms.assetid: 71fc7ebd-2e86-4a76-994b-66d3a57bcc9b
14+
caps.latest.revision: 16
15+
author: "Minewiskan"
16+
ms.author: "owend"
17+
manager: "erikre"
18+
---
19+
# Enable DirectQuery mode in SSDT
20+
21+
[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
22+
2023
In this topic, we'll describe how to enable DirectQuery mode for a tabular model project in [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)].
2124

2225
When you enable DirectQuery mode for a tabular model you're designing in SSDT:
@@ -44,7 +47,7 @@ You can create a sample partition for each table and add sample data so that you
4447
> Even in DirectQuery mode on an empty model, you can always view a small built-in rowset for each table. In [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)], click **Table** > **Table Properties** to view the 50-row dataset.
4548
4649

47-
## See Also
50+
## See also
4851
[Enable DirectQuery mode in SSMS](../../analysis-services/tabular-models/enable-directquery-mode-in-ssms.md)
4952

5053
[Add sample data to a DirectQuery model in design mode](../../analysis-services/tabular-models/add-sample-data-to-a-directquery-model-in-design-mode.md)

‎docs/analysis-services/tabular-models/enable-directquery-mode-in-ssms.md‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Enable DirectQuery mode in SSMS | Microsoft Docs"
33
ms.custom:
44
- "SQL2016_New_Updated"
5-
ms.date: "03/01/2017"
5+
ms.date: "07/06/2017"
66
ms.prod: "sql-server-2016"
77
ms.reviewer: ""
88
ms.suite: ""
@@ -17,6 +17,9 @@ ms.author: "owend"
1717
manager: "erikre"
1818
---
1919
# Enable DirectQuery mode in SSMS
20+
21+
[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
22+
2023
You can change the data access properties of a tabular model that has already been deployed, enabling DirectQuery mode, where queries execute against a backend relational data source rather than cached data residing in-memory.
2124

2225
In [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)], steps for DirectQuery configuration differ based on the model's compatibility level. Below you'll find steps that work for all compatibility levels.
@@ -123,7 +126,7 @@ manager: "erikre"
123126

124127
3. In the trace, you should see evidence of query execution on the relational database.
125128

126-
## See Also
129+
## See also
127130
[Compatibility Level for Tabular models in Analysis Services](../../analysis-services/tabular-models/compatibility-level-for-tabular-models-in-analysis-services.md)
128131
[Data Sources Supported &#40;SSAS Tabular&#41;](../../analysis-services/tabular-models/data-sources-supported-ssas-tabular.md)
129132
[Extended Events](../../relational-databases/extended-events/extended-events.md)

‎docs/analysis-services/tabular-models/test-a-model-in-directquery-mode.md‎

Lines changed: 21 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,24 @@
1-
---
2-
title: "Test a model in DirectQuery mode | Microsoft Docs"
3-
ms.custom: ""
4-
ms.date: "03/01/2017"
5-
ms.prod: "sql-server-2016"
6-
ms.reviewer: ""
7-
ms.suite: ""
8-
ms.technology:
9-
- "analysis-services"
10-
ms.tgt_pltfrm: ""
11-
ms.topic: "article"
12-
ms.assetid: 11260792-ff8b-4d0e-b845-ca210dd3fced
13-
caps.latest.revision: 11
14-
author: "Minewiskan"
15-
ms.author: "owend"
16-
manager: "erikre"
17-
---
18-
# Test a model in DirectQuery mode
1+
---
2+
title: "Test a model in DirectQuery mode | Microsoft Docs"
3+
ms.custom: ""
4+
ms.date: "07/06/2017"
5+
ms.prod: "sql-server-2016"
6+
ms.reviewer: ""
7+
ms.suite: ""
8+
ms.technology:
9+
- "analysis-services"
10+
ms.tgt_pltfrm: ""
11+
ms.topic: "article"
12+
ms.assetid: 11260792-ff8b-4d0e-b845-ca210dd3fced
13+
caps.latest.revision: 11
14+
author: "Minewiskan"
15+
ms.author: "owend"
16+
manager: "erikre"
17+
---
18+
# Test a model in DirectQuery mode
19+
20+
[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
21+
1922
Review your options for testing a tabular model in DirectQuery mode at each stage of development, starting with design.
2023

2124
## Test in Excel

0 commit comments

Comments
 (0)