An Azure relational database service.
Hi Junhui Ma,
Azure SQL Database is a fully managed PaaS service, and all OS and SQL engine patching is handled automatically by Microsoft. The service does not expose a patch history or the exact timestamps for the “last 3 patches applied” for an individual database.
To check whether platform maintenance may align with your application issues over the past 3 weeks, you can correlate the timeframe using the following supported options:
- Resource Health: Review health history for the SQL Database to identify any platform-impacting events.
https://learn.microsoft.com/azure/service-health/resource-health-overview Service Health: Check Planned Maintenance and Health history for Azure SQL Database in your region.
https://learn.microsoft.com/azure/service-health/service-health-overview Activity Log: Review the logical SQL server’s Activity Log for maintenance or failover-related operations during the impacted period.
https://learn.microsoft.com/azure/azure-monitor/essentials/activity-log- Optional: You can query recent failover or connectivity-related events using:
This view does not provide patch details and has limited retention but may help identify recent disruptions.) There is no direct method to retrieve the last 3 Azure SQL Database patch dates. The supported approach is to correlate your issue timeframe with Resource Health, Service Health, and related logs to determine any maintenance impact.SELECT TOP 50 * FROM sys.event_log ORDER BY start_time DESC;
Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help. Please do not forget to "Accept Answer" and "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.
- Optional: You can query recent failover or connectivity-related events using: