SQL Monitor 11

SQL Monitor 11.1 Release Notes

When should I upgrade?

  • We aim to release a build every two weeks that includes the latest incremental features and bug fixes. These builds are identified by a three-part version number, such as v11.0.0. So if you’ve identified a particular feature from the release notes that you need, you can download the relevant build.
  • If you want to wait until all aspects of a feature have been fully completed, it’s best to use a quarterly minor version release, identified by a two-part version number such as v11.1.
  • Annual major releases (such as v11) combine multiple feature releases and undergo additional QA.

Breaking changes

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 5; Microsoft does not support Windows Server 2012 or earlier as deployment targets for .NET 5. 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.

Version 11.1.7 - May 4, 2021

Fixes

  • Fixes a regression causing report PDF generation and emailing to fail.
  • Fixes issue sampling top queries when upgrading directly from versions of SQL Monitor older than 11.0.16

Version 11.1.6 - April 29, 2021

Features

  • Remove instance option added to unreachable instances on monitored servers page.

Fixes

  • Fix long running query alerts for Azure Managed Instance in timezones different from UTC.

Version 11.1.5 - April 22, 2021

Fixes

  • Fix regression of invalid spacing between inputs.

Version 11.1.4 - April 15, 2021

Improvements

  • You can now edit the SQL Server Connection Properties when adding an Amazon RDS SQL Server.

Fixes

  • A bug that caused the test button on the Monitored Servers page to incorrectly report failures for failover cluster instances has been fixed.
  • transaction version storage space usage will sample from SQL Server 2016 SP2 version rather than being disabled until SQL Server 2017.
  • Immediately stop displaying cards for removed instances on the global dashboard.
  • Fixed an issue with Azure Sql Databases showing duplicate cards on Global Dashboard.

Version 11.1.3 - April 8, 2021

Improvements

  • Expose thumbprint if the web server isn't authorized to access base monitor.

Fixes

  • Stops sampling the snapshot databases that were causing errors to be logged in SQL Profiler
  • Do not generate reports with a disabled schedule
  • Resolves issue with estate pages failing to display after a failed request to get data
  • Fix regression to allow specifying multiple target addresses for SNMP notifications

Version 11.1.2 - March 31, 2021

Improvements

  • Added SQL Server Metrics to Azure SQL Managed Instance overview page
  • You can now edit the SQL Server Connection Properties when adding an Azure SQL Managed Instance

Fixes

  • Fixed an issue with long queries on server overview pages not being scrollable
  • Fixed an issue with error logs and permissions failing to load for default named instances
  • Fixed an issue with alerts in sub-groups not being displayed when the top-level groups are selected
  • Fixed an issue with major version upgrades when base monitor and web frontend are installed separately

Version 11.1.1 - March 25, 2021

Features

  • SQL Server configuration options estate page: Inspect SQL Server configuration options and visualize configuration variance across your monitored instances.

Improvements

  • Removed the requirement for the account used to monitor SQL Server instance to have the db_ddladmin role for the sys.dm_db_index_physical_stats query

Fixes

  • Fixes "Server configuration options" on server overview pages showing as blank until the zoom range is changed.
  • An issue that could cause an error accessing the Azure SQL Database overview page has been fixed

Version 11.1.0 - March 18, 2021

Major changes

  • SQL Monitor no longer supports "legacy" (pre-Chromium versions) of Edge, now that Microsoft has dropped support for it.

Features

  • Azure SQL Managed Instance monitoring support is now out of preview and is fully supported. Each monitored instance will now consume one license.
  • Global dashboard now has a better 'single pane of glass' view with the ability to group by the status of instance (based on alert severity). Additionally these sections are collapsible.

Improvements

  • Affected SQL Instances list on machine unreachable alert made clickable to access respective server overview pages of the instances.
  • Added support for the "Deadlock (extended event)" alert on Azure Managed Instances.

Fixes

  • CVE-2021-27516 Updated the urijs package to 1.19.6 to address a reported vulnerability. The vulnerability has a CVSS score of 7.5 (High), but SQL Monitor's use of this library meant that it was not subject to the vulnerability. See https://www.npmjs.com/advisories/1640 for more details.
  • Fixed an issue that could cause the global dashboard to display an error when an alert was raised on an Azure Managed Instance added with the hostname,port format.
  • Fixed an issue in the PowerShell module where JSend responses from SQL Monitor were being incorrectly processed if the results of an API call were empty.
  • Fixed healthy status for Amazon RDS SQL Server instances in the global dashboard for unreachable instances.
  • An issue that could cause database file usage alerts to be incorrectly raised for databases with autogrowth enabled has been fixed.
  • The deadlock report tile can now be restricted by cluster node, using the "For:" picker on the report.
  • System databases excluded from stored procedure sampling as it was causing permission errors.
  • Fixed an issue with SQL Server error 40613 incorrectly being classified as an authorization error.
  • Fixed issue on disk usage estate page showing incorrect values when filters are changed rapidly.
  • Fixed an issue where an alert on a specific SQL Server instance inside a cluster could also appear on other cards for that cluster on the Global dashboard.


Didn't find what you were looking for?