Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: fenxu

docs/analysis-services/instances/monitor-analysis-services-with-sql-server-extended-events.md

@@ -1,7 +1,7 @@
 ---
 title: "Monitor Analysis Services with SQL Server Extended Events | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/01/2017"
+ms.date: "12/29/2017"
 ms.prod: "analysis-services"
 ms.prod_service: "analysis-services"
 ms.service: ""
@@ -28,7 +28,7 @@ manager: "kfile"
 ms.workload: "On Demand"
 ---
 # Monitor Analysis Services with SQL Server Extended Events
-[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
+[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
   Extended Events (*xEvents*) is a light-weight tracing and performance monitoring system that uses very few system resources, making it an ideal tool for diagnosing problems on both production and test servers. It's also highly scalable, configurable, and in SQL Server 2016 ,  easier to use through new built-in tool support. In SQL Server Management Studio, on connections to Analysis Services instances, you can configure, run, and monitor a live trace, similar to using SQL Server Profiler. The addition of better tooling should make xEvents a more reasonable replacement for SQL Server Profiler and creates more symmetry in how you diagnose issues in your database engine and Analysis Services workloads.  
 
  Besides [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], you can also configure  [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] Extended Event sessions the old way,  through XMLA scripting, as was supported in previous releases.  

docs/database-engine/availability-groups/windows/active-secondaries-readable-secondary-replicas-always-on-availability-groups.md

@@ -206,7 +206,7 @@ ms.workload: "On Demand"
 ##  <a name="bkmk_AccessInMemTables"></a> Accessing memory-optimized tables on a Secondary Replica  
  The transaction isolation levels that can be used with memory-optimized tables on a secondary replica are the same as on the primary replica. The recommendation is to set the session-level isolation level to READ COMMITTED and set the database-level option MEMORY_OPTIMIZED_ELEVATE_TO_SNAPSHOT to ON. For example:  
 
-```tsql  
+```sql  
 ALTER DATABASE CURRENT SET MEMORY_OPTIMIZED_ELEVATE_TO_SNAPSHOT=ON  
 GO  
 SET TRANSACTION ISOLATION LEVEL READ COMMITTED  

docs/database-engine/availability-groups/windows/configure-read-only-routing-for-an-availability-group-sql-server.md

@@ -133,13 +133,13 @@ Read-only routing is available in [!INCLUDE[sssql15](../../../includes/sssql15-m
 
  For example, the following routing list load balances read-intent connection request across two read-only replicas, `Server1` and `Server2`. The nested parentheses that surround these servers identify the load-balanced set. If neither replica is available in that set, it will proceed to attempt to sequentially connect to the other replicas, `Server3` and `Server4`, in the read-only routing list.  
 
-```tsql  
+```sql  
 READ_ONLY_ROUTING_LIST = (('Server1','Server2'), 'Server3', 'Server4')  
 ```  
 
  Note that each entry in the routing list can itself be a set of load-balanced read-only replicas. The following example demonstrates this.  
 
-```tsql  
+```sql  
 READ_ONLY_ROUTING_LIST = (('Server1','Server2'), ('Server3', 'Server4', 'Server5'), 'Server6')  
 ```  
 

docs/database-engine/availability-groups/windows/create-clustered-dtc-for-an-always-on-availability-group.md

@@ -117,7 +117,7 @@ foreach ($node in $nodes) {
 ## 3.  Configure **in-doubt xact resolution** 
 This script will configure the **in-doubt xact resolution** server configuration option to “presume commit” for in-doubt transactions.  Run the following T-SQL script in SQL Server Management Studio (SSMS) against `SQLNODE1` in **SQLCMD mode**.
 
-```tsql  
+```sql  
 /*******************************************************************
 	Execute script in its entirety on SQLNODE1 in SQLCMD mode
 *******************************************************************/
@@ -158,7 +158,7 @@ GO
 ## 4. Create test databases
 The script will create a database named `AG1` on `SQLNODE1` and a database named `dtcDemoAG1` on `SQLNODE2`.  Run the following T-SQL script in SSMS against `SQLNODE1` in **SQLCMD mode**.
 
-```tsql  
+```sql  
 /*******************************************************************
 	Execute script in its entirety on SQLNODE1 in SQLCMD mode
 *******************************************************************/
@@ -216,7 +216,7 @@ GO
 ## 5.	Create Endpoints
 This script will create an endpoint called `AG1_endpoint` that listens on TCP port `5022`.  Run the following T-SQL script in SSMS against `SQLNODE1` in **SQLCMD mode**.
 
-```tsql  
+```sql  
 /**********************************************
 Execute on SQLNODE1 in SQLCMD mode
 **********************************************/
@@ -249,7 +249,7 @@ GO
 ## 6.	Prepare databases for Availability Group
 The script will back up `AG1` on `SQLNODE1` and restore it to `SQLNODE2`.  Run the following T-SQL script in SSMS against `SQLNODE1` in **SQLCMD mode**.
 
-```tsql  
+```sql  
 /*******************************************************************
 	Execute script in its entirety on SQLNODE1 in SQLCMD mode
 *******************************************************************/
@@ -282,7 +282,7 @@ GO
 ## 7.	Create Availability Group
 [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] must be created with the **CREATE AVAILABILITY GROUP** command and the **WITH DTC_SUPPORT = PER_DB** clause.  You cannot currently alter an existing Availability Group.  The New Availability Group wizard does not allow you to enable DTC support for a new Availability Group.  The following script will create the new Availability Group and join the secondary.  Run the following T-SQL script in SSMS against `SQLNODE1` in **SQLCMD mode**.
 
-```tsql  
+```sql  
 /*******************************************************************
 	Execute script in its entirety on SQLNODE1 in SQLCMD mode
 *******************************************************************/
@@ -485,7 +485,7 @@ With the clustered DTC service completely configured, you need to stop and resta
 The first time [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] service requires a distributed transaction, it enrolls with a DTC service. SQL Server service will continue to use that DTC service until it is restarted. If a clustered DTC service is available, [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] will enroll with the clustered DTC service. If a clustered DTC service is not available, [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] will enroll with the local DTC service. In order to verify that [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] enrolls with the clustered DTC service, stop and restart each instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]. 
 
 Follow the steps contained in the T-SQL script below:
-```tsql  
+```sql  
 /*
 Gracefully cycle the SQL Server service and failover the Availability Group
 	a.	On SQLNODE2, cycle the SQL Server service from SQL Server Configuration Manger
@@ -546,7 +546,7 @@ This test uses a linked server from `SQLNODE1` to `SQLNODE2` to create a distrib
 ### Create linked servers  
 The following script will create two linked servers on `SQLNODE1`.  Run the following T-SQL script in SSMS against `SQLNODE1`.
 
-```tsql  
+```sql  
 -- SQLNODE1
 IF NOT EXISTS (SELECT * FROM sys.servers where name = N'SQLNODE1')
 BEGIN
@@ -562,7 +562,7 @@ END
 ### Execute a distributed transaction
 This script will first return the current DTC transaction statistics.  Then the script will execute a distributed transaction utilizing databases on `SQLNODE1` and `SQLNODE2`.  Then the script will again return the DTC transaction statics which will now should an increased count.  Physically connect to `SQLNODE1` and run the following T-SQL Script in SSSMS against `SQLNODE1` in **SQLCMD mode**.
 
-```tsql  
+```sql  
 /*******************************************************************
 	Execute script in its entirety on SQLNODE1 in SQLCMD mode
 	Must be physically connected to SQLNODE1

docs/database-engine/configure-windows/agent-xps-server-configuration-option.md

@@ -49,7 +49,7 @@ ms.workload: "On Demand"
 
 3.  Copy and paste the following example into the query window and click **Execute**. 
 
-```tsql 
+```sql 
 sp_configure 'show advanced options', 1;  
 GO  
 RECONFIGURE;  

docs/database-engine/configure-windows/clr-enabled-server-configuration-option.md

@@ -44,7 +44,7 @@ When you run RECONFIGURE, and the run value of the clr enabled option is changed
 ## Example  
  The following example first displays the current setting of the clr enabled option and then enables the option by setting the option value to 1. To disable the option, set the value to 0.  
 
-```tsql  
+```sql  
 EXEC sp_configure 'clr enabled';  
 EXEC sp_configure 'clr enabled' , '1';  
 RECONFIGURE;    

docs/database-engine/configure-windows/configure-the-cost-threshold-for-parallelism-server-configuration-option.md

@@ -97,7 +97,7 @@ FROM sys.dm_os_sys_info
 
 3.  Copy and paste the following example into the query window and click **Execute**. This example shows how to use [sp_configure](../../relational-databases/system-stored-procedures/sp-configure-transact-sql.md) to set the value of the `cost threshold for parallelism` option to `10`.  
 
-```tsql  
+```sql  
 USE AdventureWorks2012 ;  
 GO  
 EXEC sp_configure 'show advanced options', 1 ;  

docs/database-engine/configure-windows/configure-the-cursor-threshold-server-configuration-option.md

@@ -83,7 +83,7 @@ ms.workload: "Inactive"
 
 3.  Copy and paste the following example into the query window and click **Execute**. This example shows how to use [sp_configure](../../relational-databases/system-stored-procedures/sp-configure-transact-sql.md) to set the `cursor threshold` option to `0` so that cursor keysets are generated asynchronously.  
 
-```tsql  
+```sql  
 USE AdventureWorks2012 ;  
 GO  
 EXEC sp_configure 'show advanced options', 1 ;  

docs/database-engine/configure-windows/configure-the-default-full-text-language-server-configuration-option.md

@@ -82,7 +82,7 @@ ms.workload: "Inactive"
 
 3.  Copy and paste the following example into the query window and click **Execute**. This example shows how to use [sp_configure](../../relational-databases/system-stored-procedures/sp-configure-transact-sql.md) to set the value of the `default full-text` option to Dutch (`1043`).  
 
-```tsql  
+```sql  
 USE AdventureWorks2012 ;  
 GO  
 EXEC sp_configure 'show advanced options', 1 ;  

docs/database-engine/configure-windows/configure-the-default-language-server-configuration-option.md

@@ -75,7 +75,7 @@ ms.workload: "On Demand"
 
 3.  Copy and paste the following example into the query window and click **Execute**. This example shows how to use [sp_configure](../../relational-databases/system-stored-procedures/sp-configure-transact-sql.md) to configure the `default language` option to French (`2`).  
 
-```tsql  
+```sql  
 USE AdventureWorks2012 ;  
 GO  
 EXEC sp_configure 'default language', 2 ;