Merge pull request MicrosoftDocs#4699 from Minewiskan/ssasprofiler

PRMerger6 · web-flow · commit f8da83e48718 · 2018-01-23T12:25:38.000-08:00
Updated applies to include.
diff --git a/docs/analysis-services/instances/create-profiler-traces-for-replay-analysis-services.md b/docs/analysis-services/instances/create-profiler-traces-for-replay-analysis-services.md
@@ -1,7 +1,7 @@
 ---
 title: "Create Profiler Traces for Replay (Analysis Services) | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "01/23/2018"
 ms.prod: analysis-services
 ms.prod_service: "analysis-services"
 ms.service: ""
@@ -32,7 +32,8 @@ manager: "kfile"
 ms.workload: "Inactive"
 ---
 # Create Profiler Traces for Replay (Analysis Services)
-[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
+[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
+
   To replay queries, discovers, and commands that are submitted by users to [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)], [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] must gather the required events. In order to initiate collection of these events, appropriate event classes must be selected in the **Event Selection** tab of the **Trace Properties** dialog box. For example if the Query Begin event class is selected, events that contain queries are collected and used for replay. Also, the trace file contains sufficient information to support replaying server transactions in a distributed environment in the original sequence of transactions.  
   
 ## Replay for Queries  
diff --git a/docs/analysis-services/instances/introduction-to-monitoring-analysis-services-with-sql-server-profiler.md b/docs/analysis-services/instances/introduction-to-monitoring-analysis-services-with-sql-server-profiler.md
@@ -1,7 +1,7 @@
 ---
 title: "Introduction to Monitoring Analysis Services with SQL Server Profiler | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "01/23/2018"
 ms.prod: analysis-services
 ms.prod_service: "analysis-services"
 ms.service: ""
@@ -28,7 +28,8 @@ manager: "kfile"
 ms.workload: "Inactive"
 ---
 # Introduction to Monitoring Analysis Services with SQL Server Profiler
-[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
+[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
+
   You can use [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] to monitor events generated by an instance of [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)]. By using [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)], you can do the following:  
   
 -   Monitor the performance of an instance of [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)].  
diff --git a/docs/analysis-services/instances/use-sql-server-profiler-to-monitor-analysis-services.md b/docs/analysis-services/instances/use-sql-server-profiler-to-monitor-analysis-services.md
@@ -1,7 +1,7 @@
 ---
 title: "Use SQL Server Profiler to Monitor Analysis Services | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "01/23/2018"
 ms.prod: analysis-services
 ms.prod_service: "analysis-services"
 ms.service: ""
@@ -27,7 +27,8 @@ manager: "kfile"
 ms.workload: "On Demand"
 ---
 # Use SQL Server Profiler to Monitor Analysis Services
-[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
+[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
+
   [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] tracks engine process events, such as the start of a batch or a transaction, and it captures data about those events, thus enabling you to monitor server and database activity (for example, user queries or login activity). You can capture [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] data to a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] table or a file for later analysis, and you can also replay the events captured on the same or another [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] instance to see exactly what happened. You can replay events in real time or on a step-by-step basis. It is also very useful to run the trace events along with the Performance counters on the same machine. The profiler can correlate these two based on time and display them together along a single timeline. Trace events will give you more details while Performance counters give you an aggregate view. For information about how to create and run traces, see [Create Profiler Traces for Replay &#40;Analysis Services&#41;](../../analysis-services/instances/create-profiler-traces-for-replay-analysis-services.md).  
   
  The following table describes the topics in this section.  
