Merge pull request #28186 from WilliamDAssafMSFT/20230828-split-resource-health

20230828 split resource health

Author: v-regandowner

azure-sql/database/how-to-content-reference-guide.md

@@ -52,7 +52,7 @@ In this article you can find a content reference of various guides, scripts, and
 - [Enable e-mail notifications for automatic tuning](automatic-tuning-email-notifications-configure.md) to get information about tuning recommendations.
 - [Apply performance recommendations](database-advisor-find-recommendations-portal.md) and optimize your database.
 - [Create alerts](alerts-insights-configure-portal.md) to get notifications from Azure SQL Database.
-- [Troubleshoot connectivity](troubleshoot-common-errors-issues.md) if you notice some connectivity issues between the applications and the database. You can also use [Resource Health for connectivity issues](resource-health-to-troubleshoot-connectivity.md).
+- [Troubleshoot connectivity](troubleshoot-common-errors-issues.md) if you notice some connectivity issues between the applications and the database. You can also use [Resource Health for connectivity issues](resource-health-to-troubleshoot-connectivity.md?view=azuresql-db&preserve-view=true).
 - [Troubleshoot performance with Intelligent Insights](intelligent-insights-troubleshoot-performance.md)
 - [Manage file space](file-space-manage.md) to monitor storage usage in your database.
 - [Use Intelligent Insights diagnostics log](intelligent-insights-use-diagnostics-log.md)

azure-sql/database/media/resource-health-to-troubleshoot-connectivity/sql-resource-health-available.jpg

@@ -46,9 +46,8 @@ If your database is experiencing log-on failures, check the [Resource Health](/a
 
 The [maintenance window feature](maintenance-window.md) allows for the configuration of predictable maintenance window schedules for eligible Azure SQL databases and SQL managed instances. [Maintenance window advance notifications](../database/advance-notifications.md) are available for databases configured to use a non-default [maintenance window](maintenance-window.md). Maintenance windows and advance notifications for maintenance windows are generally available for Azure SQL Database. For Azure SQL Managed Instance, maintenance windows are generally available but advance notifications are in public preview.
 
-
 ## Next steps
 
-- Learn more about [Resource Health](resource-health-to-troubleshoot-connectivity.md) for Azure SQL Database and Azure SQL Managed Instance.
+- Learn more about [Resource Health for Azure SQL Database](resource-health-to-troubleshoot-connectivity.md?view=azuresql-db&preserve-view=true) and [Resource Health for Azure SQL Managed Instance](../managed-instance/resource-health-to-troubleshoot-connectivity.md?view=azuresql-mi&preserve-view=true).
 - For more information about retry logic, see [Retry logic for transient errors](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors).
 - Configure maintenance window schedules with the [Maintenance window](maintenance-window.md) feature.

azure-sql/database/media/resource-health-to-troubleshoot-connectivity/sql-resource-health-overview.jpg

@@ -1,72 +1,81 @@
 ---
 title: Use Azure Resource Health to monitor database health
-description: Use Azure Resource Health to monitor Azure SQL Database and Azure SQL Managed Instance health, helps you diagnose and get support when an Azure issue impacts your SQL resources.
+description: Use Azure Resource Health to monitor Azure SQL Database health, helps you diagnose and get support when an Azure issue impacts your resources.
 author: dimitri-furman
 ms.author: dfurman
 ms.reviewer: wiassaf, mathoma
-ms.date: 03/24/2021
-ms.service: sql-db-mi
+ms.date: 08/28/2023
+ms.service: sql-database
 ms.subservice: performance
 ms.topic: conceptual
 ms.custom: sqldbrb=2
 ---
-# Use Resource Health to troubleshoot connectivity for Azure SQL Database and Azure SQL Managed Instance
-[!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
+# Use Resource Health to troubleshoot connectivity for Azure SQL Database
+[!INCLUDE [appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
-[Resource Health](/azure/service-health/resource-health-overview#get-started) for Azure SQL Database and Azure SQL Managed Instance helps you diagnose and get support when an Azure issue impacts your SQL resources. It informs you about the current and past health of your resources and helps you mitigate issues. Resource Health provides technical support when you need help with Azure service issues.
+> [!div class="op_single_selector"]
+> * [Azure SQL Database](resource-health-to-troubleshoot-connectivity.md?view=azuresql-db&preserve-view=true)
+> * [Azure SQL Managed Instance](../managed-instance/resource-health-to-troubleshoot-connectivity.md?view=azuresql-mi&preserve-view=true)
 
-![A screenshot of the Azure portal showing the Resource Health page for an Azure SQL Database.](./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-overview.jpg)
+[Resource Health](/azure/service-health/resource-health-overview#get-started) for Azure SQL Database helps you diagnose and get support when an Azure issue impacts your resources. It informs you about the current and past health of your resources and helps you mitigate issues. The **Resource health** page provides technical support when you need help with Azure service issues.
+
+:::image type="content" source="./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-overview.jpg" alt-text="A screenshot of the Azure portal showing the Resource Health page for an Azure SQL Database.":::
 
 ## Health checks
 
-Resource Health determines the health of your SQL resource by examining the success and failure of logins to the resource. Currently, Resource Health for your SQL Database resource only examines login failures due to system error and not user error. The Resource Health status is updated every 1 to 2 minutes.
+**Resource health** determines the health of your SQL database by examining the success and failure of logins to the resource. Currently, **Resource health** for your SQL Database resource only examines login failures due to system error and not user error. The health status is updated every 1 to 2 minutes.
 
 ## Health states
 
 ### Available
 
-A status of **Available** means that Resource Health has not detected login failures due to system errors on your SQL resource.
+A status of **Available** means that **Resource health** has not detected login failures due to system errors on your SQL database.
 
-![A screenshot of the Azure portal showing the status messsage for the state of Available.](./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-available.jpg)
+:::image type="content" source="./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-available.jpg" alt-text="A screenshot of the Azure portal showing the status message for the state of Available.":::
 
 ### Degraded
 
-A status of **Degraded** means that Resource Health has detected a majority of successful logins, but some failures as well. These are most likely transient login errors. To reduce the impact of connection issues caused by transient login errors, implement [retry logic](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors) in your code.
+A status of **Degraded** means that **Resource health** has detected a majority of successful logins, but some failures as well. These are most likely transient login errors. To reduce the impact of connection issues caused by transient login errors, implement [retry logic](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors) in your code.
 
-![A screenshot of the Azure portal showing the status messsage for the state of Degraded.](./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-degraded.jpg)
+:::image type="content" source="./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-degraded.jpg" alt-text="A screenshot of the Azure portal showing the status message for the state of Degraded.":::
 
 ### Unavailable
 
-A status of **Unavailable** means that Resource Health has detected consistent login failures to your SQL resource. If your resource remains in this state for an extended period of time, contact support.
+A status of **Unavailable** means that **Resource health** has detected consistent login failures to your SQL database. If your resource remains in this state for an extended period of time, contact support.
 
-![A screenshot of the Azure portal showing the status messsage for the state of Unavailable.](./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-unavailable.jpg)
+:::image type="content" source="./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-unavailable.jpg" alt-text="A screenshot of the Azure portal showing the status message for the state of Unavailable.":::
 
 ### Unknown
 
-The health status of **Unknown** indicates that Resource Health hasn't received information about this resource for more than 10 minutes. Although this status isn't a definitive indication of the state of the resource, it is an important data point in the troubleshooting process. If the resource is running as expected, the status of the resource will change to Available after a few minutes. If you're experiencing problems with the resource, the Unknown health status might suggest that an event in the platform is affecting the resource.
+The health status of **Unknown** indicates that **Resource health** hasn't received information about this resource for more than 10 minutes. Although this status isn't a definitive indication of the state of the resource, it is an important data point in the troubleshooting process. If the resource is running as expected, the status of the resource will change to Available after a few minutes. If you're experiencing problems with the resource, the Unknown health status might suggest that an event in the platform is affecting the resource.
 
-![A screenshot of the Azure portal showing the status messsage for the state of Unknown.](./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-unknown.jpg)
+:::image type="content" source="./media/resource-health-to-troubleshoot-connectivity/sql-resource-health-unknown.jpg" alt-text="A screenshot of the Azure portal showing the status message for the state of Unknown.":::
 
 ## Historical information
 
-You can access up to 30 days of health history in the Health History section of Resource Health. The section will also contain the downtime reason (when available) for the downtimes reported by Resource Health. Currently, Azure shows the downtime for your database resource at a two-minute granularity. The actual downtime is likely less than a minute. The average is 8 seconds.
+You can access up to 30 days of health history in the **Health history** section of **Resource health**. The section will also contain the reason (when available) for downtimes. Currently, Azure shows the downtime for your database resource at a two-minute granularity. The actual downtime is likely less than a minute. The average is 8 seconds.
+
+## Downtime reasons
+
+When your database experiences downtime, analysis is performed to determine a reason. When available, the downtime reason is reported in the **Health history** section of **Resource health**. Downtime reasons are typically published within 45 minutes after an event.
 
-### Downtime reasons
+### Select a maintenance window
 
-When your database experiences downtime, analysis is performed to determine a reason. When available, the downtime reason is reported in the Health History section of Resource Health. Downtime reasons are typically published within 45 minutes after an event.
+You can configure your [maintenance window](maintenance-window.md?view=azuresql-db&preserve-view=true) to make impactful maintenance events predictable and less disruptive for your workload. The maintenance window feature helps you plan around predictable upgrades or scheduled maintenance. [Advance notifications](advance-notifications.md?view=azuresql-db&preserve-view=true) are available for databases configured to use a non-default maintenance window. Advance notifications enable customers to configure notifications to be sent up to 24 hours in advance of any planned event.
 
-#### Planned maintenance
+### Planned maintenance
 
-The Azure infrastructure periodically performs planned maintenance – the upgrade of hardware or software components in the datacenter. While the database undergoes maintenance, Azure SQL may terminate some existing connections and refuse new ones. The login failures experienced during planned maintenance are typically transient, and [retry logic](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors) helps reduce the impact. If you continue to experience login errors, contact support.
+The Azure infrastructure periodically performs planned maintenance – the upgrade of hardware or software components in the datacenter. While the database undergoes maintenance, Azure SQL may terminate some existing connections and refuse new ones. The login failures experienced during planned maintenance are typically transient, and [retry logic for occasional network errors](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors) helps reduce the impact. If you continue to experience login errors, contact support.
 
-#### Reconfiguration
+### Reconfiguration
 
-Reconfigurations are considered transient conditions and are expected from time to time. These events can be triggered by load balancing or software/hardware failures. Any client production application that connects to a cloud database should implement a robust connection [retry logic](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors), as it would help mitigate these situations and should generally make the errors transparent to the end user.
+Reconfigurations are considered transient conditions and are expected from time to time. These events can be triggered by load balancing or software/hardware failures. Any client production application that connects to a cloud database should implement a robust connection [retry logic for transient errors](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors), as it would help mitigate these situations and should generally make the errors transparent to the end user.
 
 ## Next steps
 
 - Learn more about [retry logic for transient errors](troubleshoot-common-connectivity-issues.md#retry-logic-for-transient-errors).
-- [Troubleshoot, diagnose, and prevent SQL connection errors](troubleshoot-common-connectivity-issues.md).
+- [Troubleshoot, diagnose, and prevent SQL connection errors](troubleshoot-common-connectivity-issues.md?view=azuresql-db&preserve-view=true).
 - Learn more about [configuring Resource Health alerts](/azure/service-health/resource-health-alert-arm-template-guide).
 - Get an overview of [Resource Health](/azure/service-health/resource-health-overview).
 - Review [Resource Health FAQ](/azure/service-health/resource-health-faq).
+- Configure a [maintenance window](maintenance-window.md?view=azuresql-db&preserve-view=true) and [advance notifications](advance-notifications.md?view=azuresql-db&preserve-view=true).

azure-sql/database/planned-maintenance.md

@@ -42,7 +42,7 @@ The following changes were added to SQL Managed Instance and the documentation i
 | **16 TB support for General Purpose preview** | Support has been added for allocation of up to 16 TB of space for SQL Managed Instance in the General Purpose service tier. See [resource limits](resource-limits.md) to learn more. This instance offer is currently in preview. |
 | **Parallel backup** | It's now possible to take backups in parallel for SQL Managed Instance in the General Purpose tier, enabling faster backups. See the [Parallel backup for better performance](https://techcommunity.microsoft.com/t5/azure-sql/parallel-backup-for-better-performance-in-sql-managed-instance/ba-p/2421762) blog entry to learn more. |
 | **Azure AD-only authentication preview** | It's now possible to restrict authentication to your Azure SQL Managed Instance only to Azure Active Directory users. This feature is currently in preview. To learn more, see [Azure AD-only authentication](../database/authentication-azure-ad-only-authentication.md). |
-| **Resource Health monitor** | Use Resource Health to monitor the health status of your Azure SQL Managed Instance. See [Resource health](../database/resource-health-to-troubleshoot-connectivity.md) to learn more. |
+| **Resource Health monitor** | Use Resource Health to monitor the health status of your Azure SQL Managed Instance. For more information, see [Resource health](../managed-instance/resource-health-to-troubleshoot-connectivity.md?view=azuresql-mi&preserve-view=true). |
 | **Granular permissions for data masking GA** | Granular permissions for dynamic data masking for Azure SQL Managed Instance is now generally available (GA). To learn more, see [Dynamic data masking](../database/dynamic-data-masking-overview.md#permissions). |
 | **User-defined routes (UDR) tables** | Service-aided subnet configuration for Azure SQL Managed Instance now makes use of service tags for user-defined routes (UDR) tables. See the [connectivity architecture](connectivity-architecture-overview.md) to learn more. |
 | **Audit management operations** | The ability to audit SQL Managed Instance operations is now generally available (GA). |

azure-sql/database/resource-health-to-troubleshoot-connectivity.md

@@ -178,7 +178,7 @@ landingContent:
           - text: Maintenance window
             url: ../database/maintenance-window.md
           - text: Resource health
-            url: ../database/resource-health-to-troubleshoot-connectivity.md
+            url: ../managed-instance/resource-health-to-troubleshoot-connectivity.md?view=azuresql-mi&preserve-view=true
 
       - linkListType: how-to-guide
         links: