Merge pull request #116711 from CarlRabeler/SQLMI_lower_case

casing for SQL MI

Author: GitHubber17

articles/azure-monitor/insights/azure-sql.md

@@ -38,9 +38,9 @@ Azure SQL Analytics is a cloud only monitoring solution supporting streaming of
 
 ## Azure SQL Analytics options
 
-The below table outlines supported options for two versions of the Azure SQL Analytics dashboard, one for single and pooled databases and elastic pools, and the other one for managed instances and instance databases.
+The below table outlines supported options for two versions of the Azure SQL Analytics dashboard, one for Azure SQL Database, and the other one for Azure SQL Managed Instance databases.
 
-| Azure SQL Analytics option | Description | Single and pooled database and elastic pools support | Managed instances and instances database support |
+| Azure SQL Analytics option | Description | SQL Database support | SQL Managed Instance support |
 | --- | ------- | ----- | ----- |
 | Resource by type | Perspective that counts all the resources monitored. | Yes | Yes |
 | Insights | Provides hierarchical drill-down into Intelligent Insights into performance. | Yes | Yes |
@@ -69,21 +69,21 @@ When you add Azure SQL Analytics to your workspace, the Azure SQL Analytics tile
 
 ![Azure SQL Analytics summary tile](./media/azure-sql/azure-sql-sol-tile-01.png)
 
-Once loaded, the tile shows the number of single and pooled databases, elastic pools, managed instances, and managed instance databases from which Azure SQL Analytics is receiving diagnostics telemetry.
+Once loaded, the tile shows the number of databases and elastic pools in SQL Database and managed instances and instance databases in SQL Managed Instance from which Azure SQL Analytics is receiving diagnostics telemetry.
 
 ![Azure SQL Analytics tile](./media/azure-sql/azure-sql-sol-tile-02.png)
 
-Azure SQL Analytics provides two separate views -- one for monitoring single databases and pooled databases and elastic pools, and the other view for monitoring managed instances and instance databases.
+Azure SQL Analytics provides two separate views -- one for monitoring SQL Database, and the other view for monitoring SQL Managed Instance.
 
-To view Azure SQL Analytics monitoring dashboard for single and pooled databases and elastic pools, click on the upper part of the tile. To view Azure SQL Analytics monitoring dashboard for managed instances and instance databases, click on the lower part of the tile.
+To view Azure SQL Analytics monitoring dashboard for SQL Database, click on the upper part of the tile. To view Azure SQL Analytics monitoring dashboard for SQL Managed Instance, click on the lower part of the tile.
 
 ### Viewing Azure SQL Analytics data
 
 The dashboard includes the overview of all databases that are monitored through different perspectives. For different perspectives to work, you must enable proper metrics or logs on your SQL resources to be streamed to Log Analytics workspace.
 
 If some metrics or logs are not streamed into Azure Monitor, the tiles in Azure SQL Analytics are not populated with monitoring information.
 
-### Single and pooled databases and elastic pools view
+### SQL Database view
 
 Once the Azure SQL Analytics tile for the database is selected, the monitoring dashboard is shown.
 
@@ -95,15 +95,15 @@ Selecting any of the tiles, opens a drill-down report into the specific perspect
 
 Each perspective in this view provides summaries at the subscription, server, elastic pool, and database levels. In addition, each perspective shows a perspective specific to the report on the right. Selecting subscription, server, pool, or database from the list continues the drill-down.
 
-### Managed instance and instances databases view
+### SQL Managed Instance view
 
 Once the Azure SQL Analytics tile for the databases is selected, the monitoring dashboard is shown.
 
 ![Azure SQL Analytics Overview](./media/azure-sql/azure-sql-sol-overview-mi.png)
 
 Selecting any of the tiles, opens a drill-down report into the specific perspective. Once the perspective is selected, the drill-down report is opened.
 
-Selecting the managed instance view, shows details on the managed instance utilization, databases it contains, and telemetry on the queries executed across the instance.
+Selecting the SQL Managed Instance view, shows details on the managed instance utilization, databases it contains, and telemetry on the queries executed across the instance.
 
 ![Azure SQL Analytics Timeouts](./media/azure-sql/azure-sql-sol-metrics-mi.png)
 
@@ -175,7 +175,7 @@ Automated alerting in Azure SQL Analytics is based on writing a Log Analytics qu
 
 You can easily [create alerts](../platform/alerts-metric.md) with the data coming from Azure SQL Database resources. Here are some useful [log queries](../log-query/log-query-overview.md) that you can use with a log alert:
 
-#### High CPU on Azure SQL Database
+#### High CPU
 
 ```
 AzureMetrics
@@ -191,7 +191,7 @@ AzureMetrics
 > - Pre-requirement of setting up this alert is that monitored databases stream basic metrics to Azure SQL Analytics.
 > - Replace the MetricName value cpu_percent with dtu_consumption_percent to obtain high DTU results instead.
 
-#### High CPU on Azure SQL Database elastic pools
+#### High CPU on elastic pools
 
 ```
 AzureMetrics
@@ -207,7 +207,7 @@ AzureMetrics
 > - Pre-requirement of setting up this alert is that monitored databases stream Basic metrics to Azure SQL Analytics.
 > - Replace the MetricName value cpu_percent with dtu_consumption_percent to obtain high DTU results instead.
 
-#### Azure SQL Database storage in average above 95% in the last 1 hr
+#### Storage in average above 95% in the last 1 hr
 
 ```
 let time_range = 1h;
@@ -251,9 +251,9 @@ AzureDiagnostics
 | distinct rootCauseAnalysis_s
 ```
 
-### Creating alerts for managed instances
+### Creating alerts for SQL Managed Instance
 
-#### Managed instance storage is above 90%
+#### Storage is above 90%
 
 ```
 let storage_percentage_threshold = 90;
@@ -269,7 +269,7 @@ AzureDiagnostics
 > - Pre-requirement of setting up this alert is that monitored the managed instance has the streaming of ResourceUsageStats log enabled to Azure SQL Analytics.
 > - This query requires an alert rule to be set up to fire off an alert when there exist results (> 0 results) from the query, denoting that the condition exists on the managed instance. The output is storage percentage consumption on the managed instance.
 
-#### Managed instance CPU average consumption is above 95% in the last 1 hr
+#### CPU average consumption is above 95% in the last 1 hr
 
 ```
 let cpu_percentage_threshold = 95;

articles/azure-sql/database/auto-failover-group-configure.md

@@ -336,19 +336,19 @@ Fail over to the secondary server:
 > [!IMPORTANT]
 > If you need to delete the secondary database, remove it from the failover group before deleting it. Deleting a secondary database before it is removed from the failover group can cause unpredictable behavior.
 
-## Managed instance in SQL Managed Instance
+## SQL Managed Instance
 
-Create a failover group between two managed instances in Azure SQL Managed Instance using the Azure portal  or PowerShell.
+Create a failover group between two managed instances in SQL Managed Instance using the Azure portal  or PowerShell.
 
-You will either need to configure [ExpressRoute](../../expressroute/expressroute-howto-circuit-portal-resource-manager.md) or to create a gateway for the virtual network of each SQL Managed Instance, connect the two gateways, and then create the failover group.
+You will either need to configure [ExpressRoute](../../expressroute/expressroute-howto-circuit-portal-resource-manager.md) or to create a gateway for the virtual network of each managed instance, connect the two gateways, and then create the failover group.
 
 ### Prerequisites
 
 Consider the following prerequisites:
 
-- The secondary SQL Managed Instance must be empty.
+- The secondary managed instance must be empty.
 - The subnet range for the secondary virtual network must not overlap the subnet range of the primary virtual network.
-- The collation and timezone of the secondary SQL Managed Instance must match that of the primary SQL Managed Instance.
+- The collation and timezone of the secondary managed instance must match that of the primary managed instance.
 - When connecting the two gateways, the **Shared Key** should be the same for both connections.
 
 ### Create primary virtual network gateway
@@ -359,29 +359,29 @@ If you have not configured [ExpressRoute](../../expressroute/expressroute-howto-
 
 Create the primary virtual network gateway using the Azure portal.
 
-1. In the [Azure portal](https://portal.azure.com), go to your resource group and select the **Virtual network** resource for your primary SQL Managed Instance.
+1. In the [Azure portal](https://portal.azure.com), go to your resource group and select the **Virtual network** resource for your primary managed instance.
 1. Select **Subnets** under **Settings** and then select to add a new **Gateway subnet**. Leave the default values.
 
-   ![Add gateway for primary SQL Managed Instance](./media/auto-failover-group-configure/add-subnet-gateway-primary-vnet.png)
+   ![Add gateway for primary managed instance](./media/auto-failover-group-configure/add-subnet-gateway-primary-vnet.png)
 
 1. Once the subnet gateway is created, select **Create a resource** from the left navigation pane and then type `Virtual network gateway` in the search box. Select the **Virtual network gateway** resource published by **Microsoft**.
 
    ![Create a new virtual network gateway](./media/auto-failover-group-configure/create-virtual-network-gateway.png)
 
-1. Fill out the required fields to configure the gateway your primary SQL Managed Instance.
+1. Fill out the required fields to configure the gateway your primary managed instance.
 
-   The following table shows the values necessary for the gateway for the primary SQL Managed Instance:
+   The following table shows the values necessary for the gateway for the primary managed instance:
 
     | **Field** | Value |
     | --- | --- |
-    | **Subscription** |  The subscription where your primary SQL Managed Instance is. |
+    | **Subscription** |  The subscription where your primary managed instance is. |
     | **Name** | The name for your virtual network gateway. |
-    | **Region** | The region where your primary SQL Managed Instance is. |
+    | **Region** | The region where your primary managed instance is. |
     | **Gateway type** | Select **VPN**. |
     | **VPN Type** | Select **Route-based** |
     | **SKU**| Leave default of `VpnGw1`. |
-    | **Location**| The location where your secondary SQL Managed Instance and secondary virtual network is.   |
-    | **Virtual network**| Select the virtual network for your secondary SQL Managed Instance. |
+    | **Location**| The location where your secondary managed instance and secondary virtual network is.   |
+    | **Virtual network**| Select the virtual network for your secondary managed instance. |
     | **Public IP address**| Select **Create new**. |
     | **Public IP address name**| Enter a name for your IP address. |
     |   |   |
@@ -430,19 +430,19 @@ Create the secondary virtual network gateway using the Azure portal or PowerShel
 
 # [Portal](#tab/azure-portal)
 
-Repeat the steps in the previous section to create the virtual network subnet and gateway for the secondary SQL Managed Instance. Fill out the required fields to configure the gateway for your secondary SQL Managed Instance.
+Repeat the steps in the previous section to create the virtual network subnet and gateway for the secondary managed instance. Fill out the required fields to configure the gateway for your secondary managed instance.
 
-The following table shows the values necessary for the gateway for the secondary SQL Managed Instance:
+The following table shows the values necessary for the gateway for the secondary managed instance:
 
    | **Field** | Value |
    | --- | --- |
-   | **Subscription** |  The subscription where your secondary SQL Managed Instance is. |
+   | **Subscription** |  The subscription where your secondary managed instance is. |
    | **Name** | The name for your virtual network gateway, such as `secondary-mi-gateway`. |
-   | **Region** | The region where your secondary SQL Managed Instance is. |
+   | **Region** | The region where your secondary managed instance is. |
    | **Gateway type** | Select **VPN**. |
    | **VPN Type** | Select **Route-based** |
    | **SKU**| Leave default of `VpnGw1`. |
-   | **Location**| The location where your secondary SQL Managed Instance and secondary virtual network is.   |
+   | **Location**| The location where your secondary managed instance and secondary virtual network is.   |
    | **Virtual network**| Select the virtual network that was created in section 2, such as `vnet-sql-mi-secondary`. |
    | **Public IP address**| Select **Create new**. |
    | **Public IP address name**| Enter a name for your IP address, such as `secondary-gateway-IP`. |
@@ -501,8 +501,8 @@ Create connections between the two gateways using the Azure portal.
 1. On the **Basics** tab, select the following values and then select **OK**.
     1. Select `VNet-to-VNet` for the **Connection type**.
     1. Select your subscription from the drop-down.
-    1. Select the resource group for your SQL Managed Instance in the drop-down.
-    1. Select the location of your primary SQL Managed Instance from the drop-down.
+    1. Select the resource group for your managed instance in the drop-down.
+    1. Select the location of your primary managed instance from the drop-down.
 1. On the **Settings** tab, select or enter the following values and then select **OK**:
     1. Choose the primary network gateway for the **First virtual network gateway**, such as `Primary-Gateway`.  
     1. Choose the secondary network gateway for the **Second virtual network gateway**, such as `Secondary-Gateway`.
@@ -547,27 +547,27 @@ Create connections between the two gateways using PowerShell.
 
 ### Create the failover group
 
-Create the failover group for your SQL Managed Instances using the Azure portal or PowerShell.
+Create the failover group for your managed instances using the Azure portal or PowerShell.
 
 # [Portal](#tab/azure-portal)
 
-Create the failover group for your SQL Managed Instances using Azure portal.
+Create the failover group for your managed instances using Azure portal.
 
 1. Select **Azure SQL** in the left-hand menu of the [Azure portal](https://portal.azure.com). If **Azure SQL** is not in the list, select **All services**, then type Azure SQL in the search box. (Optional) Select the star next to **Azure SQL** to favorite it and add it as an item in the left-hand navigation.
-1. Select the primary SQL Managed Instance you want to add to the failover group.  
+1. Select the primary managed instance you want to add to the failover group.  
 1. Under **Settings**, navigate to **Instance Failover Groups** and then choose to **Add group** to open the **Instance Failover Group** page.
 
    ![Add a failover group](./media/auto-failover-group-configure/add-failover-group.png)
 
-1. On the **Instance Failover Group** page, type the name of your failover group and then choose the secondary SQL Managed Instance from the drop-down. Select **Create** to create your failover group.
+1. On the **Instance Failover Group** page, type the name of your failover group and then choose the secondary managed instance from the drop-down. Select **Create** to create your failover group.
 
    ![Create failover group](./media/auto-failover-group-configure/create-failover-group.png)
 
 1. Once failover group deployment is complete, you will be taken back to the **Failover group** page.
 
 # [PowerShell](#tab/azure-powershell)
 
-Create the failover group for your SQL Managed Instances using PowerShell.
+Create the failover group for your managed instances using PowerShell.
 
    ```powershell-interactive
    $primaryResourceGroupName = "<Primary-Resource-Group>"
@@ -596,17 +596,17 @@ Test failover of your failover group using the Azure portal or PowerShell.
 
 Test failover of your failover group using the Azure portal.
 
-1. Navigate to your _secondary_ SQL Managed Instance within the [Azure portal](https://portal.azure.com) and select **Instance Failover Groups** under settings.
-1. Review which SQL Managed Instance is the primary, and which SQL Managed Instance is the secondary.
+1. Navigate to your _secondary_ managed instance within the [Azure portal](https://portal.azure.com) and select **Instance Failover Groups** under settings.
+1. Review which managed instance is the primary, and which managed instance is the secondary.
 1. Select **Failover** and then select **Yes** on the warning about TDS sessions being disconnected.
 
    ![Fail over the failover group](./media/auto-failover-group-configure/failover-mi-failover-group.png)
 
 1. Review which manged instance is the primary and which instance is the secondary. If failover succeeded, the two instances should have switched roles.
 
-   ![SQL Managed Instances have switched roles after failover](./media/auto-failover-group-configure/mi-switched-after-failover.png)
+   ![Managed instances have switched roles after failover](./media/auto-failover-group-configure/mi-switched-after-failover.png)
 
-1. Go to the new _secondary_ SQL Managed Instance and select **Failover** once again to fail the primary instance back to the primary role.
+1. Go to the new _secondary_ managed instance and select **Failover** once again to fail the primary instance back to the primary role.
 
 # [PowerShell](#tab/azure-powershell)
 
@@ -625,7 +625,7 @@ Test failover of your failover group using PowerShell.
    Get-AzSqlDatabaseInstanceFailoverGroup -ResourceGroupName $primaryResourceGroupName `
        -Location $secondaryLocation -Name $failoverGroupName
 
-   # Failover the primary SQL Managed Instance to the secondary role
+   # Failover the primary managed instance to the secondary role
    Write-host "Failing primary over to the secondary location"
    Get-AzSqlDatabaseInstanceFailoverGroup -ResourceGroupName $secondaryResourceGroupName `
        -Location $secondaryLocation -Name $failoverGroupName | Switch-AzSqlDatabaseInstanceFailoverGroup
@@ -635,7 +635,7 @@ Test failover of your failover group using PowerShell.
    Get-AzSqlDatabaseInstanceFailoverGroup -ResourceGroupName $primaryResourceGroupName `
        -Location $secondaryLocation -Name $failoverGroupName
 
-   # Fail primary SQL Managed Instance back to primary role
+   # Fail primary managed instance back to primary role
    Write-host "Failing primary back to primary role"
    Get-AzSqlDatabaseInstanceFailoverGroup -ResourceGroupName $primaryResourceGroupName `
        -Location $primaryLocation -Name $failoverGroupName | Switch-AzSqlDatabaseInstanceFailoverGroup