Merge pull request #110261 from dialmoth/patch-9

Update maintenance-scheduling.md

Author: Jak-MS

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

@@ -21,12 +21,13 @@ For example, you can schedule a primary window of Saturday 22:00 to Sunday 01:00
 
 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.
 
-Although a maintenance window can be between three and eight hours this does not mean the data warehouse will be offline for the duration. Maintenance can occur at any time within that window and you should expect a single disconnect during that period lasting ~5 -6 mins as the service deploys new code to your data warehouse. DW400c and lower may experience multiple brief losses in connectivity at various times during the maintenance window. When maintenance starts, all active sessions will be canceled, and non-committed transactions will be rolled back. To minimize instance downtime, make sure that your data warehouse has no long-running transactions before your chosen maintenance period.
+When choosing a maintenance window, you need to select a start time and set a maximum duration. The "maximum duration of a maintenance window" determines the timeframe in which maintenance tasks will be carried out. This timeframe can be between three (3) and eight (8) hours, with a minimum requirement of three (3) hours. During this period, your data warehouse will be temporarily offline as your dedicated pool is moved to upgraded capacity using a process similar to pause/resume. Under typical conditions, this operation will complete in well under 30 minutes, but it's important to note that in some cases, it can take longer. For instance, if there are active transactions when the maintenance begins, they will be canceled and rolled back, potentially causing delays in restoring the online service. To prevent this situation, we recommend ensuring that there are no long-running transactions active at the start of your maintenance window.
 
 All maintenance operations should finish within the specified maintenance windows unless we are required to deploy a time sensitive update. If your data warehouse is paused during a scheduled maintenance, it will be updated during the resume operation. You'll be notified immediately after your data warehouse maintenance is completed.
 
 > [!NOTE]
-> The maintenance windows are not applicable for DW400c or lower performance levels. They can undergo maintenance at any time.
+> - The maintenance windows are not applicable for DW400c or lower performance levels. They can undergo maintenance at any time.
+> - DW400c and lower may experience multiple brief losses in connectivity at various times during the maintenance window.
 
 ## Alerts and monitoring