SRP-13108 Delays database backup overdue alerts being raised to allow for availability group DMVs to be initialized
SRP-13086 Handle monitoring errors raised when a database becomes unavailable that were previously putting the monitored server into a stopped monitoring state.
Resolves an issue during base monitor startup when the data repository is not available
Eliminated some monitoring queries when it's known up-front that they won't return any monitoring data.
Improved the performance of global dashboard
Starting with SQL Monitor v10.2, SQL Monitor base monitors can no longer be installed on Windows Server 2012 or earlier. For the time being, this only affects the base monitor. Support for running the SQL Monitor website on Windows Server 2012 or earlier will be removed in the future.
We've moved to .NET Core 3.1; Microsoft do not support Windows Server 2012 or earlier as deployment targets for .NET Core 3.1. This also means that SQL Monitor base monitors cannot be installed on unsupported desktop operating systems. Refer to Microsoft's installation guidance for specific versions.
You can monitor the same versions of Windows and SQL Server that you've always monitored. However, base monitors need to be installed on Windows Server 2012 R2 or newer.
Resolves an issue with some tiles of the example report failing to load
#168702 Resolves an issue with displaying Query History Details in SQL Monitor with Azure Databases.
SRP-13077 Reduce frequency of DBCC calls
7670 - The Cluster, Standalone Machine, AzureSqlServer, and AmazonRdsSqlServer classes contain Group property (please download updated powershell module)
Added database graph to tempdb
Added temporary table usage to tempdb section
Tips and how-to guides for Redgate products
Ask, discuss, and solve questions about Redgate's tools
Meet us at an event, get sponsored, and join our Friends of Redgate
In-depth articles and opinion from Redgate's technical journal