SQL Monitor 5

SQL Monitor 3.0 release notes

SQL Monitor - May 8th, 2012


  • SRP-4797/SRP-5031: Database appearing offline or SQL Monitor collection failing.
  • SRP-4106: Monitoring fails but is solved by restarting the Base Monitor.

SQL Monitor - April 3rd, 2012


  • SRP-6380: Alert settings email override settings not working.
  • SRP-6398: Cannot edit custom metrics on some installations.

SQL Monitor - March 22nd, 2012

Upgrading to SQL Monitor 3.0

SQL Monitor 3.0 is a major upgrade from SQL Monitor 2.3. If your current license includes a valid support and upgrades package for SQL Monitor 2.x, the same license serial number will automatically activate SQL Monitor 3.0.

If your v2.x license does not include support and upgrades, SQL Monitor will upgrade to a 14-day trial of v3.0. You cannot roll back to the previous 2.x version, so we recommend that you install a trial version of v3.0 on a separate machine. For more information, see Upgrading to a later version of SQL Monitor.

New features

  • Custom metrics: SQL Monitor collects a standard set of metrics from every monitored object. Custom metrics allow you to use your own T-SQL queries to collect metric values that aren't currently collected by default. They can also be used to collect application-specific information. Once collected, you can analyze and alert on this data.
  • Example custom metrics: To get you started with custom metrics, we have provided examples that include validated T-SQL queries so you don't have to write your own scripts.
  • User roles: Administrators can now control user access to certain features in SQL Monitor. There are three user roles available; Administrator, Standard and Read-only. Each role is activated by creating a single password and then sharing it with relevant users. The following restrictions apply:
    • Administrators have unrestricted access and can configure every feature in SQL Monitor.
    • Standard users can manage and configure alerts, but cannot configure custom metrics, custom alerts or alert email settings. They can view most pages except the Manage user roles, Licensing and Base Monitor connection pages.
    • Read-only users cannot make any configuration changes, but they can view most of the pages in SQL Monitor except the Manage user roles, Licensing and Base Monitor connection pages.
  • SQL 2012 / Denali support: You can monitor SQL Server 2012 servers within SQL Monitor.
  • Analysis graph improvements: Graphs will no longer interpolate the data where there are significant gaps, so you can see more clearly whetherdata collection issues exist.
  • Feature usage reporting: This feature (disabled by default) helps Red Gate understand how you are using SQL Monitor. It reports how often individual features are used, allowing future development work to be prioritized. You will be asked during the installation if you wish to enable feature usage reporting. For more information, see: Data collected by the Quality Improvement Program.

Known issues

  • IIS path change: If you are using SQL Monitor with IIS, the path containing your website files will have changed and you will need to reconfigure your website settings. The new path is displayed during the installation.
  • Side by side installs: It is not possible to run SQL Monitor 3.0 side by side with earlier versions.
  • SRP-1443: An internal error occurs if the database name contains a non-latin character.
  • SRP-6122: Database size metric returns zero for instance during restore.
  • SRP-4106: Monitoring fails but is solved by restarting the Base Monitor.
  • SRP-3222: Issue making WMI calls despite changing authentication level to Pkt_Privacy.

Didn't find what you were looking for?