Merge pull request #10593 from Minewiskan/compat-level-update

Update to compatibility levels article.

Author: PRMerger9

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

@@ -1,6 +1,6 @@
 ---
 title: "Compatibility level for tabular models in Analysis Services | Microsoft Docs"
-ms.date: 05/23/2019
+ms.date: 06/10/2019
 ms.prod: sql
 ms.technology: analysis-services
 ms.custom: tabular-models
@@ -13,22 +13,24 @@ manager: kfile
 # Compatibility level for Analysis Services tabular models
 [!INCLUDE[ssas-appliesto-sqlas-aas](../../includes/ssas-appliesto-sqlas-aas.md)]
 
-  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.
+  The *compatibility level* refers to functionality and feature enhancements in both the Analysis Services engine and in tabular model metadata. In-general, you should choose the latest compatibility level supported by your servers. 
 
   **The latest supported compatibility level is 1400** 
 
 Major features in the 1400 compatibility level include:
 
 *  New infrastructure for data connectivity and import into tabular models with support for TOM APIs and TMSL scripting. This enables support for additional data sources such as Azure Blob storage. Additional data sources will be included in future updates.
-*  Data transformation and data mashup capabilities by using Get Data and M expressions in SSDT.
-*  Measures now support a Detail Rows property with a DAX expression, enabling BI tools such as Microsoft Excel drill-down to detailed data from an aggregated report. For example, when end-users view total sales for a region and month, they can view the associated order details. 
+*  Data transformation and data mashup capabilities by using Get Data and M expressions in SQL Server Data Tools (SSDT).
+*  Measures now support a Detail Rows property with a DAX expression, enabling BI tools such as Microsoft Excel drill down to detailed data from an aggregated report. For example, when users view total sales for a region and month, they can view the associated order details. 
 *  Object-level security for table and column names, in addition to the data within them.
 *  Enhanced support for ragged hierarchies.
 *  Performance and monitoring improvements.
 
 
 ## Supported compatibility levels by version
 
+Lower compatibility levels are supported for backwards compatibility. 
+
 |||  
 |-|-|- 
 |**Compatibility level**|**Server version**| 
@@ -38,7 +40,7 @@ Major features in the 1400 compatibility level include:
 |1103|SQL Server 2017*, SQL Server 2016, SQL Server 2014, SQL Server 2012 SP1|  
 |1100|SQL Server 2017*, SQL Server 2016, SQL Server 2014, SQL Server 2012 SP1, SQL Server 2012| 
 
-\* 1100 and 1103 compatibility levels are deprecated in SQL Server 2017.
+\* 1100 and 1103 compatibility levels are deprecated in SQL Server 2017 and later.
 
 ## Set compatibility level 
  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.