Fixed an issue when the customers have hundreds of agents, the table records grow very fast. And 'registry_registry_value' and 'registry_registry_variable' take more than 1TB. | |
Fixed an issue where the DB agent log might print password information as Pa$$word, even if the value has been encrypted. | |
Fixed an issue where on-demand data connections might fail unless more TCP ports are opened. | |
Fixed an issue when using customized email setting, email might not be sent for the Alarm SQL_AZURE - Database Unresponsive. | |
Disabled the alarm SQL_AZURE - Blockers Connections Baseline Deviation by default. | |
Disabled the alarm SQL_AZURE - All Active Connections Baseline Deviation by default. |
Azure PI dashboard cannot be accessed if the PI repository uses non-default port. | |
PI engine didn't use new credential changed in Connection Details dashboard. Workaround: Reactive the agent after changing the credential. | |
When the monitored user is not an admin, the database is DTU, and the service tier is basic, standard s0, or standard s1, User cannot see data in Blocking (Current) dashboard and there is no data in PI dashboard. | |
Workaround: Upgrade agent on Agent Status dashboard. | |
Azure cannot change RMI setting in Administration. Workaround: Refer to KB: https://support.quest.com/foglight/kb/312636/cannot-update-rmi-for-azure-sql-agent. | |
An error log showed in FMS log for loading heatmap component in FMS version before 5.9.3. | |
Agent does not support MFA (Multi-Factor_Authentication) connections to Azure databases. | |
Databases - SQL PI dashboard does not display an Azure SQL database agent configured with SQL PI. |
The following is a list of third party issues known to exist at the time of this release.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center