1. Why have we removed the Diagnostic Settings dependency in Azure SQL Database monitor?
- Till APM v15240:
- Azure SQL Database was using Diagnostic Settings to perform data collection.
- Prerequisites had to be fulfilled to turn on Diagnostic Settings for data collection.
- A Diagnostic Storage Account to be provided in edit monitor page to facilitate data collection.
- From APM v15240:
- Azure SQL Database monitor has been enhanced to use Azure APIs and the Diagnostic Settings dependency has been removed.
- There are no perquisites for data collection.
- Diagnostic Storage Account details in the edit monitor page need not be given to facilitate data collection.
2. What happens in Applications Manager when you delete Azure SQL Database in the Azure portal?
- When an Azure SQL Database is deleted in Azure portal, the monitor status depends on the 'Action on Deleted Resources' option.
- Continue Alerting: The monitor will continue generating alerts indicating that the Azure SQL Database has been deleted.
- Stop Alerting: The monitor will stop generating alerts about the deleted Azure SQL Database.
- Unmanage Resource: The monitor will transition to an unmanaged state.
- Delete Resource: The monitor will be removed entirely from Applications Manager.
- Furthermore, an entry will be added in Audit logs upon deletion of Azure monitors in Applications Manager. You can check this under Settings → Tools → Audit logs → choose Actions as 'Azure Monitors Deletion'.
3. DTU (Database Transaction Unit) based metrics are specific for DTU-based SQL Databases: