Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into F1tweaks

Author: markingmyname

.acrolinx-config.edn

@@ -1,2 +1,2 @@
 {:allowed-branchname-matches ["master" "release-.*" "sandbox-.*"]
- :allowed-filename-matches ["docs" "docs-msdn"]}
+ :allowed-filename-matches ["(?i)^docs/(?:(?!toc.yml))" "docs-msdn"]}

docs/analytics-platform-system/appliance-topology.md

@@ -15,7 +15,7 @@ Displays summary information on the entire Analytics Platform System.
 
 The page lists a read-only version of all the hosts and fabric nodes in the current appliance including their Ethernet and Infiniband IP addresses.  
 
-![SQL_Server_PDW_DWConfig_ApplTop](./media/appliance-topology/SQL_Server_PDW_DWConfig_ApplTop.png "SQL_Server_PDW_DWConfig_ApplTop")  
+![Screenshot of the Microsoft Analytics Platform System Configuration Manager dialog box showing the Appliance Topology.](./media/appliance-topology/SQL_Server_PDW_DWConfig_ApplTop.png "SQL_Server_PDW_DWConfig_ApplTop")  
 
 ## See Also  
 [Launch the Configuration Manager (Analytics Platform System)](launch-the-configuration-manager.md)  

docs/analytics-platform-system/configure-scom-to-monitor-analytics-platform-system.md

@@ -34,52 +34,52 @@ Here are detailed instructions on how to do the tasks:
 
     1.  Navigate to the **Administration** pane, right-click on **Run As Configuration** -> **Accounts** and select **Create Run As Account...**  
 
-        ![ConfigureScomCreateRunAsAccount](./media/configure-scom-to-monitor-analytics-platform-system/ConfigureScomCreateRunAsAccount.png "ConfigureScomCreateRunAsAccount")  
+        ![Screenshot showing the Create Run As Account option.](./media/configure-scom-to-monitor-analytics-platform-system/ConfigureScomCreateRunAsAccount.png "ConfigureScomCreateRunAsAccount")  
 
     2.  The **Create Run As Account Wizard** dialog will open. On the **Introduction** page, click **Next**.  
 
     3.  On the **General Properties** page, select **Windows** from **Run As Account type** and specify "APS Watcher" as the **Display name**.  
 
-        ![CreateRunAsAccountWizardGeneralProperties](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardGeneralProperties.png "CreateRunAsAccountWizardGeneralProperties")  
+        ![Screenshot showing the General Properties page of the Create Run As Account Wizard.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardGeneralProperties.png "CreateRunAsAccountWizardGeneralProperties")  
 
     4.  On the **Credentials** page,
-        ![CreateRunAsAccountWizardCredentials](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardCredentials.png "CreateRunAsAccountWizardCredentials")  
+        ![Screenshot showing the Credentials page of the Create Run As Account Wizard.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardCredentials.png "CreateRunAsAccountWizardCredentials")  
 
     5.  On the **Distribution Security** page, select **Less secure** and click the **Create** button to finish.  
 
-        ![CreateRunAsAccountWizardDistributionSecurity](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardDistributionSecurity.png "CreateRunAsAccountWizardDistributionSecurity")  
+        ![Screenshot showing the Distribution Security page of the Create Run As Account Wizard.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardDistributionSecurity.png "CreateRunAsAccountWizardDistributionSecurity")  
 
         1.  If you decide to use the **More secure** option, you have to manually specify computers to which credentials will be distributed. To do this, after creating the Run As account, right-click on it and select **Properties**.  
 
         2.  Navigate to the **Distribution** tab and **Add** desired computers.  
 
-            ![RunAsAccountProperties](./media/configure-scom-to-monitor-analytics-platform-system/RunAsAccountProperties.png "RunAsAccountProperties")  
+            ![Screenshot showing the Run As Account Properties dialog box.](./media/configure-scom-to-monitor-analytics-platform-system/RunAsAccountProperties.png "RunAsAccountProperties")  
 
 2.  Set the **Microsoft APS Watcher Account** profile to use **APS Watcher** Run As account.  
 
     1.  Navigate to **Administration** -> **Run As Configuration** -> **Profiles**.  
 
-        ![AdministrationRunAsConfigurationProfiles](./media/configure-scom-to-monitor-analytics-platform-system/AdministrationRunAsConfigurationProfiles.png "AdministrationRunAsConfigurationProfiles")  
+        ![Screenshot showing the Profiles option.](./media/configure-scom-to-monitor-analytics-platform-system/AdministrationRunAsConfigurationProfiles.png "AdministrationRunAsConfigurationProfiles")  
 
     2.  Right click on **Microsoft APS Watcher Account** from the list and select **Properties**.  
 
-        ![MicrosoftApsWatcherAccountProperties](./media/configure-scom-to-monitor-analytics-platform-system/MicrosoftApsWatcherAccountProperties.png "MicrosoftApsWatcherAccountProperties")  
+        ![Screenshot showing the Properties option.](./media/configure-scom-to-monitor-analytics-platform-system/MicrosoftApsWatcherAccountProperties.png "MicrosoftApsWatcherAccountProperties")  
 
     3.  The **Run As Profile Wizard** dialog will open. Skip the **Introduction** page by clicking **Next**.  
 
     4.  On the **General Properties** page, click **Next**.  
 
     5.  On the **Run As Accounts** page, click the **Add...** button and select the previously created **APS Watcher** Run As account.  
 
-        ![RunAsProfileWizardAdd](./media/configure-scom-to-monitor-analytics-platform-system/RunAsProfileWizardAdd.png "RunAsProfileWizardAdd")  
+        ![Screenshot showing the Add a Run As Account dialog box.](./media/configure-scom-to-monitor-analytics-platform-system/RunAsProfileWizardAdd.png "RunAsProfileWizardAdd")  
 
     6.  Click **Save** to finish profile assignment.  
 
 3.  Wait until APS appliances discovery completes.  
 
     1.  Navigate to the **Monitoring** pane and open the **SQL Server Appliance** -> **Microsoft Analytics Platform System** -> **Appliances** state view.  
 
-        ![SqlServerApplianceMicrosoftApsAppliances](./media/configure-scom-to-monitor-analytics-platform-system/SqlServerApplianceMicrosoftApsAppliances.png "SqlServerApplianceMicrosoftApsAppliances")  
+        ![Screenshot showing the Appliances option.](./media/configure-scom-to-monitor-analytics-platform-system/SqlServerApplianceMicrosoftApsAppliances.png "SqlServerApplianceMicrosoftApsAppliances")  
 
     2.  Wait until the appliance appears in the list. The name of the appliance should be equal to one specified in the registry. After discovery completes you should see all appliances listed but not monitored. To enable monitoring, follow the next steps.  
 
@@ -92,11 +92,11 @@ Here are detailed instructions on how to do the tasks:
 
     2.  On the **General Properties** page, select **Basic Authentication** account type.  
 
-        ![CreateRunAsAccountWizardGeneralProperties2](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardGeneralProperties2.png "CreateRunAsAccountWizardGeneralProperties2")  
+        ![Screenshot showing the General Properties page of the Create Run As Account Wizard with Basic Authentication selected from the Run As Account type dropdown.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardGeneralProperties2.png "CreateRunAsAccountWizardGeneralProperties2")  
 
     3.  On the **Credentials** page, supply valid credentials to access APS health state DMVs.  
 
-        ![CreateRunAsAccountWizardCredentials2](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardCredentials2.png "CreateRunAsAccountWizardCredentials2")  
+        ![Screenshot showing the Credentials page of the Create Run As Account Wizard with valid credentials wo access APS health state DMVs.](./media/configure-scom-to-monitor-analytics-platform-system/CreateRunAsAccountWizardCredentials2.png "CreateRunAsAccountWizardCredentials2")  
 
 5.  Configure the **Microsoft APS Action Account** profile to use the newly created Run As account for the APS instance.  
 
@@ -105,7 +105,7 @@ Here are detailed instructions on how to do the tasks:
     2.  On the **Run As Accounts** page, click **Add...** and 
     3.  select the newly created Run As account.  
 
-        ![RunAsProfileWizardAdd2](./media/configure-scom-to-monitor-analytics-platform-system/RunAsProfileWizardAdd2.png "RunAsProfileWizardAdd2")  
+        ![Screenshot showing the Add a Run As Account dialog box with APS Action selected from the Run As account dropdown list.](./media/configure-scom-to-monitor-analytics-platform-system/RunAsProfileWizardAdd2.png "RunAsProfileWizardAdd2")  
 
 ## Next Step  
 Now that you have configured the Management Packs, you are ready to start monitoring the appliance. For more information, see [Monitor the Appliance by Using System Center Operations Manager (Analytics Platform System)](monitor-the-appliance-by-using-system-center-operations-manager.md).  

docs/analytics-platform-system/launch-the-configuration-manager.md

@@ -40,7 +40,7 @@ After the **Configuration Manager** is started, you will see all available funct
 
 To close and exit **Configuration Manager**, click **Exit** in the lower-right corner of any screen.  
 
-![SQL_Server_PDW_DWConfig_ApplTop](./media/launch-the-configuration-manager/SQL_Server_PDW_DWConfig_ApplTop.png "SQL_Server_PDW_DWConfig_ApplTop")  
+![Screenshot of the Microsoft Analytics Platform System Configuration Manager dialog box showing the Appliance Topology.](./media/launch-the-configuration-manager/SQL_Server_PDW_DWConfig_ApplTop.png "SQL_Server_PDW_DWConfig_ApplTop")  
 
 ## See Also  
 [Monitor the Appliance by Using the Admin Console (Analytics Platform System)](monitor-the-appliance-by-using-the-admin-console.md)  

docs/azure-data-studio/extensions/kusto-extension.md

@@ -8,7 +8,7 @@ author: markingmyname
 ms.author: maghan
 ms.reviewer: jukoesma
 ms.custom: 
-ms.date: 09/22/2020
+ms.date: 10/29/2020
 ---
 
 # Kusto (KQL) extension for Azure Data Studio (Preview)
@@ -127,11 +127,9 @@ The [SandDance extension](sanddance-extension.md) with the Kusto (KQL) extension
 
 | Details | Workaround |
 |---------|------------|
-| [Kusto connection Viewlet after reload doesn't work](https://github.com/microsoft/azuredatastudio/issues/12475). | N/A |
-| [Unable to reconnect automatically](https://github.com/microsoft/azuredatastudio/issues/11830). | Disconnect and reconnect to the Azure Data Explorer cluster. |
-| [Refresh Kusto cluster doesn't seem to reconnect properly](https://github.com/microsoft/azuredatastudio/issues/11824). | Disconnect and reconnect to the Azure Data Explorer cluster. |
-| [Connect to a cluster should bring up cluster dashboard instead of database](https://github.com/microsoft/azuredatastudio/issues/12549) | N/A |
-| For each table in your Azure Data cluster database, there's only an option to **SELECT TOP 1000** instead of **TAKE 10**. | N/A |
+| [In Kusto notebook, Changing a database connection on a saved alias connection is stuck after an error in code cell execution](https://github.com/microsoft/azuredatastudio/issues/12384) | Close and reopen the Notebook, then connect to the right cluster with the database |
+| [In Kusto Notebook, changing a database connection on a non-saved alias connection doesn't work](https://github.com/microsoft/azuredatastudio/issues/12843) |Create a new connection from Connection Viewlet and save it with an alias. Then create a new notebook and connect to the newly saved connection) | 
+| [In Kusto Notebook, the database dropdown isn't populated when creating a new ADX connection](https://github.com/microsoft/azuredatastudio/issues/12666) | Create a new connection from Connection Viewlet and save it with an alias. Then create a new notebook and connect to the newly saved connection) |
 
 You can file a [feature request](https://github.com/microsoft/azuredatastudio/issues/new?assignees=&labels=&template=feature_request.md&title=) to provide feedback to the product team.  
 You can file a [bug](https://github.com/microsoft/azuredatastudio/issues/new?assignees=&labels=&template=bug_report.md&title=) to provide feedback to the product team.

docs/azure-data-studio/notebooks/notebooks-kqlmagic.md

@@ -8,7 +8,7 @@ author: markingmyname
 ms.author: maghan
 ms.reviewer: jukoesma
 ms.custom: 
-ms.date: 04/27/2020
+ms.date: 10/29/2020
 ---
 
 # Kqlmagic in Azure Data Studio
@@ -254,5 +254,4 @@ Learn more about notebooks and Kqlmagic:
 - [Use a Jupyter Notebook and Kqlmagic extension to analyze data in Azure Data Explorer](/azure/data-explorer/Kqlmagic)
 - [Extension (Magic) to Jupyter notebook and Jupyter lab](https://github.com/Microsoft/jupyter-Kqlmagic), that enable notebook experience working with Kusto, Application Insights, and LogAnalytics data.
 - [Kqlmagic](https://pypi.org/project/Kqlmagic/)
-- [KustoMagicSamples](https://notebooks.azure.com/RknDzgn/projects/KustoMagicSamples/html/Getting%20Started%20with%20Kqlmagic%20on%20Azure%20Data%20Explorer-Copy.ipynb)
-- [How to use notebooks in Azure Data Studio](./notebooks-guidance.md)
+- [How to use notebooks in Azure Data Studio](./notebooks-guidance.md)

docs/azure-data-studio/preview-features.md

@@ -72,7 +72,7 @@ You can enable or disable preview features anytime in your Settings.
 ### First-party extensions in preview
 
 * Admin Pack for SQL Server
-* Azure SQL Data Warehouse Insights
+* Azure Synapse Analytics Insights
 * Central Management Servers
 * Database Administration Tool Extensions for Windows
 * Kusto

docs/azure-data-studio/tutorial-qds-sql-server.md

@@ -131,7 +131,7 @@ To add the *slow queries widget* to your dashboard, edit the *dashboard.database
 
 5. View the query's execution plan:
 
-   ![showplan](./media/tutorial-qds-sql-server/showplan.png)
+   ![Screenshot showing the query's execution plan.](./media/tutorial-qds-sql-server/showplan.png)
 
 ## Next steps
 

docs/azure-data-studio/tutorial-sql-editor.md

@@ -61,11 +61,11 @@ Azure Data Studio provides many built-in T-SQL snippets for quickly creating sta
 
 2. Type **sql** in the editor, arrow down to **sqlCreateStoredProcedure**, and press the *Tab* key (or *Enter*) to load the create stored procedure snippet.
 
-   ![snippet-list](./media/tutorial-sql-editor/snippet-list.png)
+   ![Screenshot showing the Query Editor with sql typed in the editor and the sqlCreateStoredProcedure option called out.](./media/tutorial-sql-editor/snippet-list.png)
 
 3. The create stored procedure snippet has two fields set up for quick edit, *StoredProcedureName* and *SchemaName*. Select *StoredProcedureName*, right-click, and select **Change All Occurrences**. Now type *getCustomer* and all *StoredProcedureName* entries change to *getCustomer*.
 
-   ![snippet](./media/tutorial-sql-editor/snippet.png)
+   ![Screenshot showing the Query Editor with the Change All Occurrences option called out.](./media/tutorial-sql-editor/snippet.png)
 
 5. Change all occurrences of *SchemaName* to *dbo*. 
 6. The snippet contains placeholder parameters and body text that needs updating. The *EXECUTE* statement also contains placeholder text because it doesn't know how many parameters the procedure will have. For this tutorial update the snippet so it looks like the following code:

docs/big-data-cluster/cluster-troubleshooter-notebooks.md

@@ -75,7 +75,7 @@ A set of notebooks for repairing known situations and states of a SQL Server Big
 |Name |Description |
 |---|---|---|---|
 |TSG005 - Forwarding loop detected|Use this notebook to dealing with forwarding loop detected since the utility dnsmasq can put a local loopback in resolv.conf, which can cause the controller pods to go into a CrashLoopBackOff during initial cluster deployment: https://askubuntu.com/questions/627899/nameserver-127-0-1-1-in-resolv-conf-wont-go-away|
-|TSG011 - Restart sparkhistory server|Use this notebook to restart sparkhistory server since the sparkhistory java process can hang during startup. Restarting the sparkhistory server (supervisorctl restart sparkhistory) can resolve this issue.|
+|TSG011 - Restart sparkhistory server|Use this notebook to restart sparkhistory server since the sparkhistory java process can stop responding during startup. Restarting the sparkhistory server (supervisorctl restart sparkhistory) can resolve this issue.|
 |TSG018 - Kill sqlservr process on the master pool| Use this notebook when T-SQL SHUTDOWN does not successfully re-cycle the ./sqlservr process. Use this notebook to kill the main sqlservr process which will get automatically restarted by the ./sqlservr front end process.|
 |TSG024 - Namenode is in safe mode| Use this notebook when HDFS gets itself into Safe mode. For example if too many Pods are re-cycled too quickly in the Storage Pool then Safe mode may be automatically enabled.|
 |TSG028 - Restart node manager on all storage pool nodes| Use this notebook when needs to restart node manager on all storage pool nodes.|
@@ -99,4 +99,3 @@ A set of notebooks for repairing known situations and states of a SQL Server Big
 ## Next steps
 
 For more information about big data clusters, see [What are [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)]](big-data-cluster-overview.md).
-