Skip to content

Commit 8e18995

Browse files
authored
Update planned-maintenance.md
1 parent 1a44b86 commit 8e18995

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/azure-sql/database/planned-maintenance.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ Learn how to prepare for planned maintenance events on your database in Azure SQ
2020

2121
## What is a planned maintenance event?
2222

23+
To keep Azure SQL Database and Azure SQL Managed Instance services secure, compliant, stable, and performant, updates are being performed through the service components almost continuously. Thanks to the modern and robust service architecture and innovative technologies like [hot patching](https://aka.ms/azuresqlhotpatching), majority of updates are fully transparent and non-impactful in terms of service availability. Still, few types of updates cause short service interrupts and require special treatment.
24+
2325
For each database, Azure SQL Database and Azure SQL Managed Instance maintain a quorum of database replicas where one replica is the primary. At all times, a primary replica must be online servicing, and at least one secondary replica must be healthy. During planned maintenance, members of the database quorum will go offline one at a time, with the intent that there is one responding primary replica and at least one secondary replica online to ensure no client downtime. When the primary replica needs to be brought offline, a reconfiguration/failover process will occur in which one secondary replica will become the new primary.
2426

2527
## What to expect during a planned maintenance event

0 commit comments

Comments
 (0)