SQL Monitor 4.1 release notes
Published 08 July 2015
4.1.2 - April 7th, 2015
- Redesigned installer
- Connection no longer fails when using using an availability group listener due to incorrect SQL Server error log path
- Minor optimization to query wait sampling
When you upgrade to this version, the settings in the config file RedGate.Response.Engine.Alerting.Base.Service.exe.settings.config aren't preserved.
- If you upgrade from SQL Monitor 3.x or earlier, the settings in the config file (by default located in %ProgramData\Red Gate\SQL Monitor <previous major version number>) aren't copied to the new config file for V4 (by default located in %ProgramData\Red Gate\SQL Monitor 4).
- If you upgrade from SQL Monitor 4.x, the settings in the config file (by default located in %ProgramData\Red Gate\SQL Monitor 4) are overwritten.
4.1.1 - February 18th, 2015
- Volume labels for disks on monitored servers are appended to their corresponding drive letters
- SRP-9495: Loading data animation now disappears after a top-ten query on a SQL Server instance overview page is clicked and cleared
- SRP-9378, SRP-9426: Base Monitor can attempt to reconnect automatically after authentication failure (enabled with a config file option)
4.1.0 - June 12th, 2014
- Support for monitoring and base repository on SQL Server 2014.
- Registry key can now fully disable error reporting.
- Issue with JSON serialization and a large number of databases is fixed.
- Issue with deadlock parsing is fixed.
- Parameter sniffing problem is fixed.
- Monitoring of AlwaysOn Availability Groups is improved.
- SRP-9395 - SQL Monitor no longer keeps locks on SQL Server error log files.
- SRP-9399 - Wait stats now work correctly with a case sensitive Data Repository.
- SRP-9401 - Wait stats now work correctly when monitoring SQL Server 2014.
After adding a cluster to monitor, the Resources section may not display any information. To fix this, restart the Base Monitor service. For more information, see the troubleshooting page Resources section is empty.