Understanding Maintenance in Azure SQL
summary
Azure SQL does platform maintenance for OS, firmware and the SQL engine and enacts it by patching secondaries then failing the primary to a healthy replica so databases see roughly every ~35 days a maintenance cycle that can cause a short failover the final reconfiguration averages <8 second reconnection for new connections while long queries must restart and clients should implement retries (error 46 113). Choose a custom window (defaults 5–8pm region) to enable advanced notifications (24h) and expect backups, patches and reboots during that window.
AI-written summary · about
chapters (17)
- 0:00Introduction to session
- 1:24Speaker background
- 2:25Azure SQL PaaS offerings
- 4:12Microsoft-managed tasks
- 4:54Automatic updates explained
- 5:38Planned maintenance events
- 7:24Maintenance impact and retry logic
- 9:12Maintenance frequency and timing
- 10:17Choosing maintenance windows
- 11:43Importance of custom windows
- 12:25Maintenance window contents
- 13:27Critical patch handling
- 14:08Advanced notifications
- 15:11Offer types for notifications
- 15:56Setting up notifications
- 17:19Your remaining tasks in Azure SQL
- 18:42Security and data value
related talks
46mAzure SQL Database Business Continuity During Disaster
47mPerfecting business continuity for Azure SQL DB
01h 01mAzure SQL Database-Business Continuity During Disaster
50mDiscover what's new in Azure SQL Managed Instance through an exciting Demo Party!
50mSQL Server to Azure SQL: Performance and Availability
49mSQL Server and Windows Server Better together on Azure
46mBusiness continuity of on-prem SQL Servers using Azure services through Arc
54mDesigning Azure Data Disaster Recovery Strategies