Merge pull request #105766 from julieMSFT/rebrandscreenshots

Rebrandscreenshots

Author: PMEds28

articles/sql-data-warehouse/maintenance-scheduling.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Synapse Analytics maintenance schedules
+title: Maintenance schedules for Synapse SQL pool
 description: Maintenance scheduling enables customers to plan around the necessary scheduled maintenance events that Azure Synapse Analytics uses to roll out new features, upgrades, and patches.  
 services: sql-data-warehouse
 author: antvgski
@@ -14,11 +14,11 @@ ms.reviewer: jrasnick
 
 # Use maintenance schedules to manage service updates and maintenance
 
-The maintenance schedule feature integrates the Service Health Planned Maintenance Notifications, Resource Health Check Monitor, and maintenance scheduling service for SQL Analytics within Azure Synapse. 
+The maintenance schedule feature integrates the Service Health Planned Maintenance Notifications, Resource Health Check Monitor, and maintenance scheduling service for Synapse SQL pool (data warehouse) within Azure Synapse Analytics. 
 
 You should use maintenance scheduling to choose a time window when it's convenient to receive new features, upgrades, and patches. You will need to choose a primary and a secondary maintenance window within a seven-day period, each window must be within separate day ranges.
 
-For example, you can schedule a primary window of Saturday 22:00 to Sunday 01:00, and then schedule a secondary window of Wednesday 19:00 to 22:00. If SQL Analytics can't perform maintenance during your primary maintenance window, it will try the maintenance again during your secondary maintenance window. Service maintenance could on occasion occur during both the primary and secondary windows. To ensure rapid completion of all maintenance operations, DW400c and lower data warehouse tiers could complete maintenance outside of a designated maintenance window.
+For example, you can schedule a primary window of Saturday 22:00 to Sunday 01:00, and then schedule a secondary window of Wednesday 19:00 to 22:00. If maintenance can't be performed during your primary maintenance window, it will try the maintenance again during your secondary maintenance window. Service maintenance could on occasion occur during both the primary and secondary windows. To ensure rapid completion of all maintenance operations, DW400c and lower data warehouse tiers could complete maintenance outside of a designated maintenance window.
 
 All newly created data warehouse instances will have a system-defined maintenance schedule applied during deployment. The schedule can be edited as soon as deployment is complete.
 
@@ -29,45 +29,43 @@ All maintenance operations should finish within the specified maintenance window
 ## Alerts and monitoring
 
 Integration with Service Health notifications and the Resource Health Check Monitor allows customers to stay informed of impending maintenance activity. This automation takes advantage of Azure Monitor. You can decide how you want to be notified of impending maintenance events. Also, you can choose which automated flows will help you manage downtime and minimize operational impact.
+
 A 24-hour advance notification precedes all maintenance events that aren't for the DWC400c and lower tiers.
 
 > [!NOTE]
 > In the event we are required to deploy a time critical update, advanced notification times may be significantly reduced.
 
-If you received an advance notification that maintenance will take place, but SQL Analytics can't perform maintenance during that time, you'll receive a cancellation notification. Maintenance will then resume during the next scheduled maintenance period.
+If you received advance notification that maintenance will take place, but maintenance can't be performed during the time period in the notification, you'll receive a cancellation notification. Maintenance will then resume during the next scheduled maintenance period.
 
 All active maintenance events appear in the **Service Health - Planned Maintenance** section. The Service Health history includes a full record of past events. You can monitor maintenance via the Azure Service Health check portal dashboard during an active event.
 
 ### Maintenance schedule availability
 
-Even if maintenance scheduling isn't available in your selected region, you can view and edit your maintenance schedule at any time. When maintenance scheduling becomes available in your region, the identified schedule will immediately become active on your data warehouse.
+Even if maintenance scheduling isn't available in your selected region, you can view and edit your maintenance schedule at any time. When maintenance scheduling becomes available in your region, the identified schedule will immediately become active on your Synapse SQL pool.
 
 ## View a maintenance schedule 
 
-### Portal
-
 By default, all newly created data warehouse instances have an eight-hour primary and secondary maintenance window applied during deployment. As indicated above, you can change the windows as soon deployment is complete. No maintenance will take place outside the specified maintenance windows without prior notification.
 
-To view the maintenance schedule that has been applied to your data warehouse, complete the following steps:
+To view the maintenance schedule that has been applied to your Synapse SQL pool, complete the following steps:
 
 1.	Sign in to the [Azure portal](https://portal.azure.com/).
-2.	Select the data warehouse that you want to view. 
-3.	The selected data warehouse opens on the overview blade. The maintenance schedule that's applied to the data warehouse appears below **Maintenance schedule**.
+2.	Select the Synapse SQL pool that you want to view. 
+3.	The selected Synapse SQL pool opens on the overview blade. The maintenance schedule that's applied to the data warehouse appears below **Maintenance schedule**.
 
 ![Overview blade](media/sql-data-warehouse-maintenance-scheduling/clear-overview-blade.PNG)
 
 ## Change a maintenance schedule 
 
-### Portal
-A maintenance schedule can be updated or changed at any time. If the selected instance is going through an active maintenance cycle, the settings will be saved. They'll become active during the next identified maintenance period. [Learn more](https://docs.microsoft.com/azure/service-health/resource-health-overview) about monitoring your data warehouse during an active maintenance event. 
+A maintenance schedule can be updated or changed at any time. If the selected instance is going through an active maintenance cycle, the settings will be saved. They'll become active during the next identified maintenance period. [Learn more](../service-health/resource-health-overview.md) about monitoring your data warehouse during an active maintenance event. 
 
-### Identifying the primary and secondary windows
+## Identifying the primary and secondary windows
 
 The primary and secondary windows must have separate day ranges. An example is a primary window of Tuesday–Thursday and a secondary of window of Saturday–Sunday.
 
-To change the maintenance schedule for your data warehouse, complete the following steps:
+To change the maintenance schedule for your Synapse SQL pool, complete the following steps:
 1.	Sign in to the [Azure portal](https://portal.azure.com/).
-2.	Select the data warehouse that you want to update. The page opens on the overview blade. 
+2.	Select the Synapse SQL pool that you want to update. The page opens on the overview blade. 
 3.	Open the page for maintenance schedule settings by selecting the **Maintenance Schedule summary** link on the overview blade. Or, select the **Maintenance Schedule** option on the left-side resource menu.  
 
     ![Overview blade options](media/sql-data-warehouse-maintenance-scheduling/maintenance-change-option.png)
@@ -88,10 +86,10 @@ During preview, some regions might not yet support the full set of available **D
 
    If you're saving a schedule in a region that doesn't support maintenance scheduling, the following message appears. Your settings are saved and become active when the feature becomes available in your selected region.    
 
-   ![Message about region availability](media/sql-data-warehouse-maintenance-scheduling/maintenance-notactive-toast.png)
+   ![Message about region availability](media/sql-data-warehouse-maintenance-scheduling/maintenance-not-active-toast.png)
 
 ## Next steps
-- [Learn more](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitor-alerts-unified-usage) about creating, viewing, and managing alerts by using Azure Monitor.
-- [Learn more](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitor-alerts-unified-log-webhook) about webhook actions for log alert rules.
-- [Learn more](https://docs.microsoft.com/azure/monitoring-and-diagnostics/monitoring-action-groups) Creating and managing Action Groups.
-- [Learn more](https://docs.microsoft.com/azure/service-health/service-health-overview) about Azure Service Health.
+- [Learn more](../monitoring-and-diagnostics/monitor-alerts-unified-usage.md) about creating, viewing, and managing alerts by using Azure Monitor.
+- [Learn more](../monitoring-and-diagnostics/monitor-alerts-unified-log-webhook.md) about webhook actions for log alert rules.
+- [Learn more](../monitoring-and-diagnostics/monitoring-action-groups.md) Creating and managing Action Groups.
+- [Learn more](../service-health/service-health-overview.md) about Azure Service Health.