Merge pull request MicrosoftDocs#4702 from MicrosoftDocs/master

v-alje · web-flow · commit 3206a31870f8 · 2018-01-23T15:31:50.000-08:00
1/23 PM Publish
diff --git a/docs/analysis-services/instances/TOC.md b/docs/analysis-services/instances/TOC.md
@@ -17,15 +17,15 @@
 ## [HTTP Access](configure-http-access-to-analysis-services-on-iis-8-0.md)  
 ## [Client libraries (data providers)](data-providers-used-for-analysis-services-connections.md)  
 ## [Disconnect users and sessions](disconnect-users-and-sessions-on-analysis-services-server.md)  
-# [Monitor an Analysis Services Instance](monitor-an-analysis-services-instance.md)  
+# Monitor Analysis Services
 ## [SQL Server Profiler](use-sql-server-profiler-to-monitor-analysis-services.md)  
-### [Introduction to Monitoring Analysis Services with SQL Server Profiler](introduction-to-monitoring-analysis-services-with-sql-server-profiler.md)  
-### [Create Profiler Traces for Replay (Analysis Services)](create-profiler-traces-for-replay-analysis-services.md)  
+### [Monitoring Analysis Services with SQL Server Profiler](introduction-to-monitoring-analysis-services-with-sql-server-profiler.md)  
+### [Create Profiler Traces for Replay](create-profiler-traces-for-replay-analysis-services.md)  
 ## [Extended Events](monitor-analysis-services-with-sql-server-extended-events.md)  
 ## [Dynamic Management Views (DMVs) ](use-dynamic-management-views-dmvs-to-monitor-analysis-services.md)  
 ## [Performance Counters](performance-counters-ssas.md)  
 ## [Clear the Analysis Services Caches](clear-the-analysis-services-caches.md)  
-# [Script Administrative Tasks](script-administrative-tasks-in-analysis-services.md)  
+# Script Administrative Tasks
 ## [Create Scripts in Management Studio](create-analysis-services-scripts-in-management-studio.md)  
 ### [Use Analysis Services Templates in SQL Server Management Studio](use-analysis-services-templates-in-sql-server-management-studio.md)  
 ### [Use the Analysis Services Scripts Project in Management Studio](analysis-services-scripts-project-in-sql-server-management-studio.md)  
diff --git a/docs/analysis-services/instances/analysis-services-scripts-project-in-sql-server-management-studio.md b/docs/analysis-services/instances/analysis-services-scripts-project-in-sql-server-management-studio.md
@@ -29,7 +29,8 @@ manager: "kfile"
 ms.workload: "Inactive"
 ---
 # Analysis Services Scripts Project in SQL Server Management Studio
-[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
+[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
+
   In [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)], you can create an Analysis Server Scripts project in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] to group related scripts together for development, management, and source control purposes. If no solution is currently loaded in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], creating a new Analysis Server Scripts project automatically creates a new solution. Otherwise, the new Analysis Server Scripts project can be added to the existing solution or created in a new solution.  
   
  You use the following basic steps to create an Analysis Server Scripts project in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)]:  
diff --git a/docs/analysis-services/instances/connect-to-analysis-services.md b/docs/analysis-services/instances/connect-to-analysis-services.md
@@ -1,7 +1,7 @@
 ---
 title: "Connect to Analysis Services | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/07/2017"
+ms.date: "01/23/2018"
 ms.prod: analysis-services
 ms.prod_service: "analysis-services"
 ms.service: ""
@@ -26,6 +26,8 @@ ms.workload: "On Demand"
 # Connect to Analysis Services
 [!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
   Use the information in this section to learn about connection string properties, client libraries used for connections, which authentication methods are supported by Analysis Services, and how to set up or clear connections before taking a server offline.  
+
+To learn about connecting to Azure Analysis Services, see [Connect to a server](https://docs.microsoft.com/azure/analysis-services/analysis-services-connect).
   
 ## Analysis Services connections  
  Analysis Services uses TCP as the network protocol and XML for Analysis (XMLA) as a communication protocol. At the lowest level, all of the client libraries provided with Analysis Services implementing XMLA-over-TCP. Although it is possible to build applications based on raw XMLA, most applications and application developers use client libraries to take advantage of the object models and coding efficiencies that they provide. For client connections to Analysis Services, you can use IIS as an intermediary connection if you cannot use TCP across the stack. One advantage of using HTTP access via IIS is the ability to connect from applications that pass credentials on the connection string.  
diff --git a/docs/analysis-services/instances/create-analysis-services-scripts-in-management-studio.md b/docs/analysis-services/instances/create-analysis-services-scripts-in-management-studio.md
@@ -26,7 +26,8 @@ manager: "kfile"
 ms.workload: "Inactive"
 ---
 # Create Analysis Services Scripts in Management Studio
-[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
+[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
+
   [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] includes script generation features, templates, and editors that you can use to script Analysis Services objects and tasks.  
   
 ## Script Analysis Services Tasks in Management Studio  
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/data-providers-used-for-analysis-services-connections.md b/docs/analysis-services/instances/data-providers-used-for-analysis-services-connections.md
@@ -1,7 +1,7 @@
 ---
 title: "Data providers used for Analysis Services connections | Microsoft Docs"
 ms.custom: ""
-ms.date: "12/06/2017"
+ms.date: "01/23/2018"
 ms.prod: analysis-services
 ms.prod_service: "analysis-services"
 ms.service: ""
@@ -22,12 +22,12 @@ manager: "kfile"
 ms.workload: "On Demand"
 ---
 # Client libraries (data providers) used for Analysis Services connections
-[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
+[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
 
-Analysis Services provides three client libraries, also known as **data providers**, for server and data access from tools and client applications. Tools like SSMS and SSDT, and applications like Power BI Desktop and Excel connect to Analysis Services by using these libraries. Two of the client libraries, ADOMD.NET and Analysis Services Management Objects (AMO), are managed client libraries. The Analysis Services OLE DB provider (MSOLAP DLL) is a native client library. 
+Analysis Services provides three client libraries, also known as **data providers**, for server and data access from tools and client applications. Tools like SSMS and SSDT, and applications like Power BI Desktop and Excel connect to Analysis Services by using these libraries. Two of the client libraries, ADOMD.NET and Analysis Services Management Objects (AMO), are managed client libraries. The Analysis Services OLE DB provider (MSOLAP DLL) is a native client library. Client libraries are the same for both SQL Server Analysis Services and Azure Analysis Services.
   
 ##  <a name="bkmk_downloadsite"></a> Where to get newer versions  
- The version installed on the client computer should match the major version of the server providing the data. If the server installation is newer than the data providers installed on the workstations in your network, you might need to install newer libraries.  
+ The version installed on a client computer should match the major version of the server providing the data. If the server installation is newer than the data providers installed on the workstations in your network, you might need to install newer libraries.  
 
 Client libraries included in earlier SQL Server Feature Packs correspond to that SQL version; however, they may not be the latest. Connecting to Azure Analysis Services may require later versions. All versions are backward compatible.
 
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/schedule-ssas-administrative-tasks-with-sql-server-agent.md b/docs/analysis-services/instances/schedule-ssas-administrative-tasks-with-sql-server-agent.md
@@ -32,7 +32,7 @@ ms.workload: "On Demand"
 ## Prerequisites  
  SQL Server Agent service must be installed.  
   
- By default, jobs run under the service account. In [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)], the default account for SQL Server Agent is NT Service\SQLAgent$\<instancename>. To perform a backup or processing task, this account must be a system administrator on the Analysis Services instance. For more information, see [Grant server admin rights to an  Analysis Services instance](../../analysis-services/instances/grant-server-admin-rights-to-an-analysis-services-instance.md).  
+ By default, jobs run under the service account. The default account for SQL Server Agent is NT Service\SQLAgent$\<instancename>. To perform a backup or processing task, this account must be a system administrator on the Analysis Services instance. For more information, see [Grant server admin rights to an  Analysis Services instance](../../analysis-services/instances/grant-server-admin-rights-to-an-analysis-services-instance.md).  
   
  You should also have a test database to work with. You can deploy the AdventureWorks multidimensional sample database or a project from the Analysis Services multidimensional tutorial to use in this walkthrough. For more information, see [Install Sample Data and Projects for the Analysis Services Multidimensional Modeling Tutorial](../../analysis-services/install-sample-data-and-projects.md).  
   
diff --git a/docs/analysis-services/instances/use-analysis-services-templates-in-sql-server-management-studio.md b/docs/analysis-services/instances/use-analysis-services-templates-in-sql-server-management-studio.md
@@ -22,7 +22,8 @@ manager: "kfile"
 ms.workload: "Inactive"
 ---
 # Use Analysis Services Templates in SQL Server Management Studio
-[!INCLUDE[ssas-appliesto-sqlas](../../includes/ssas-appliesto-sqlas.md)]
+[!INCLUDE[ssas-appliesto-sqlas-all-aas](../../includes/ssas-appliesto-sqlas-all-aas.md)]
+
   [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] provides a set of templates to help you quickly create XMLA scripts, DMX or MDX queries, create KPIs in a cube or tabular model, script backup and restore operations, and perform many other tasks. Templates are located in the **Template Explorer** in [!INCLUDE[ssManStudio](../../includes/ssmanstudio-md.md)].  
   
  This topic includes a list of the templates for multidimensional models and tabular models, and provides examples of how to build an MDX query and XMLA statement by using the Metadata Explorer and the Template Explorer.  
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.  
diff --git a/docs/analysis-services/server-properties/memory-properties.md b/docs/analysis-services/server-properties/memory-properties.md
@@ -1,7 +1,7 @@
 ---
 title: "Memory Properties | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/17/2016"
+ms.date: "01/23/2018"
 ms.prod: analysis-services
 ms.prod_service: "analysis-services"
 ms.service: ""
@@ -37,8 +37,10 @@ ms.workload: "On Demand"
   [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] preallocates a modest amount of memory at start up so that requests can be handled immediately. Additional memory is allocated as query and processing workloads increase. 
   
   By specifying configuration settings, you can control the thresholds at which memory is released. For example, the **HardMemoryLimit** setting specifies a self-imposed out-of-memory condition (by default, this threshold is not enabled), where new requests are rejected outright until more resources become available.
+
+To learn more about maximum memory utilized per Analysis Services instance by edition, see [Editions and supported features of SQL Server](../../sql-server/editions-and-components-of-sql-server-2017.md#Cross-BoxScaleLimits).
   
- **Applies to:** Multidimensional and Tabular server mode, unless noted otherwise.  
+ The following settings apply to both multidimensional and tabular server mode unless noted otherwise.  
  
 ## Default memory configuration
 
@@ -143,5 +145,3 @@ When set to 1, processing is less likely to fail due to memory constraints becau
 ## See Also  
  [Server Properties in Analysis Services](../../analysis-services/server-properties/server-properties-in-analysis-services.md)   
  [Determine the Server Mode of an Analysis Services Instance](../../analysis-services/instances/determine-the-server-mode-of-an-analysis-services-instance.md)  
-  [SQL Server 2008 R2 Analysis Services Operations Guide](http://go.microsoft.com/fwlink/?LinkID=225539)
-  
diff --git a/docs/integration-services/TOC.md b/docs/integration-services/TOC.md
@@ -25,11 +25,11 @@
 
 # [Lift and shift SSIS packages to Azure](lift-shift/ssis-azure-lift-shift-ssis-packages-overview.md)
 ## [Tutorial - Deploy, run, and monitor a package on Azure](lift-shift/ssis-azure-deploy-run-monitor-tutorial.md)
-## [Connect to the SSIS Catalog on Azure](lift-shift/ssis-azure-connect-to-catalog-database.md)
-## [Schedule package execution on Azure](lift-shift/ssis-azure-schedule-packages.md)
-## [Validate packages deployed to Azure](lift-shift/ssis-azure-validate-packages.md)
 ## [Connect to data sources with Windows Authentication](lift-shift/ssis-azure-connect-with-windows-auth.md)
 ## [Connect to files and file shares](lift-shift/ssis-azure-files-file-shares.md)
+## [Validate packages deployed to Azure](lift-shift/ssis-azure-validate-packages.md)
+## [Connect to the SSIS Catalog on Azure](lift-shift/ssis-azure-connect-to-catalog-database.md)
+## [Schedule package execution on Azure](lift-shift/ssis-azure-schedule-packages.md)
 
 # [Install or upgrade](../integration-services/install-windows/install-integration-services.md)
 
@@ -175,11 +175,8 @@
 #### [Lesson 3-3 - Testing the Deployed Packages](lesson-3-3-testing-the-deployed-packages.md)
 
 # Resources
-## Follow the blog
-### [SSIS team blog](https://blogs.msdn.microsoft.com/ssis/)
-## Get help
-### [SSIS forum on MSDN](https://social.msdn.microsoft.com/Forums/home?forum=sqlintegrationservices)
-### [SSIS tag on Stack Overflow](http://stackoverflow.com/questions/tagged/ssis)  
-## Give feedback
-### [SQL Server feedback forum](https://feedback.azure.com/forums/908035-sql-server)  
+## [Get help in the SSIS forum](https://social.msdn.microsoft.com/Forums/home?forum=sqlintegrationservices)
+## [Get help on Stack Overflow](http://stackoverflow.com/questions/tagged/ssis)  
+## [Follow the SSIS team blog](https://blogs.msdn.microsoft.com/ssis/)
+## [Report issues & request features](https://feedback.azure.com/forums/908035-sql-server)
 ## [Get the docs on your PC](../sql-server/sql-server-help-installation.md)
diff --git a/docs/integration-services/sql-server-integration-services.md b/docs/integration-services/sql-server-integration-services.md
@@ -40,12 +40,9 @@ ms.workload: "Active"
 - [![Download from Evaluation Center](../includes/media/download2.png)](../ssdt/download-sql-server-data-tools-ssdt.md) [Download SQL Server Data Tools (SSDT)](../ssdt/download-sql-server-data-tools-ssdt.md)
 - [![Download from Evaluation Center](../includes/media/download2.png)](../ssms/download-sql-server-management-studio-ssms.md) [Download SQL Server Management Studio (SSMS)](../ssms/download-sql-server-management-studio-ssms.md)
 
-##  ![info_tip](../sql-server/media/info-tip.png) Get Help
- 
-- [MSDN forum for SSIS - ask questions](https://social.msdn.microsoft.com/Forums/home?forum=sqlintegrationservices)
-- [MSDN forum for SSDT and SSMS - ask questions](https://social.msdn.microsoft.com/Forums/home?forum=sqltool)
-- [Stack Overflow (tag *ssis*) - ask questions](http://stackoverflow.com/questions/tagged/ssis)
-- [Microsoft Connect - report bugs and request features](https://connect.microsoft.com/SQLServer/Feedback)
-- [Reddit - general discussion about SSIS](https://www.reddit.com/r/SQLServer/search?q=ssis&restrict_sr=on)
-- [Microsoft support options for business users](https://support.microsoft.com/gp/support-options-for-business)
-- [Contact Microsoft options for business user](https://support.microsoft.com/gp/contactus81?Audience=Commercial)
+##  ![info_tip](../sql-server/media/info-tip.png) Resources
+-   [Get help in the SSIS forum](https://social.msdn.microsoft.com/Forums/home?forum=sqlintegrationservices)
+-   [Get help on Stack Overflow](http://stackoverflow.com/questions/tagged/ssis)  
+-   [Follow the SSIS team blog](https://blogs.msdn.microsoft.com/ssis/)
+-   [Report issues & request features](https://feedback.azure.com/forums/908035-sql-server)
+-   [Get the docs on your PC](../sql-server/sql-server-help-installation.md)
diff --git a/docs/linux/tutorial-sql-server-containers-kubernetes.md b/docs/linux/tutorial-sql-server-containers-kubernetes.md
diff --git a/docs/relational-databases/databases/database-instant-file-initialization.md b/docs/relational-databases/databases/database-instant-file-initialization.md
diff --git a/docs/sql-server/editions-and-components-of-sql-server-2017.md b/docs/sql-server/editions-and-components-of-sql-server-2017.md
