SQL Monitor 5

SQL Monitor 2.3 release notes

May 26th, 2011

New features

  • Top 10 expensive queries – the 10 queries that use the most resource based on Execution Count, Duration, CPU Time, Physical Reads, Logical Reads and Logical Writes are now displayed on the SQL Server Instance and Database overview pages. This data is also available in the Alert Details page for SQL Server alerts.
  • Data purging – SQL Monitor now supports explicit purge options for high volume data channels. Note: Purge options that were customized in earlier versions will be translated accordingly. You should review your purge settings after upgrade.
  • Analysis page – The Analysis page now supports high resolution graphs and can plot a maximum of 500 data points.
  • Performance improvements have been made to the Base Monitor and UI.
  • SQL Monitor now works with PagerDuty.
  • Emails for Job duration unusual and Job failure alerts now contain job name.
  • Monitoring error (host machine data collection) and Monitoring error (SQL Server data collection) alerts now have a two minute time tolerance before they are raised.
  • Long running query alert now contains database name and query duration.
  • Behavior change for Job duration unusual alert. It now validates the “Ignore less than“ value against the current run job duration instead of the base line.

Fixes

  • SRP-3645: Monitoring error (host machine data collection) and Monitoring error (SQL Server data collection) alerts are too sensitive.
  • SRP-3614: Cannot set a SQL connection port greater than 32767.
  • SRP-3483:Processor utilization alert can be raised for disabled alert levels.
  • SRP-2905: Include query duration for Long running query alert.
  • SRP-3688: Analysis graph plots data but not the lines when the custom time range goes further back than the data available..
  • SRP-3036: Trace statements in the SQL Processes / Profiler trace tab are not chronologically ordered.
  • SRP-2969: Trace information in 2.2 less than 1.3.
  • SRP-3090: Offline alerts: include seconds on alert timings.
  • SRP-2472:Job failed and Job duration unusual alert email does not contain job name.
  • SRP-2924: Allow more than 100 percent for job duration unusual configuration.
  • SRP-3399:Blocked process and Long running query alert pages do not display database name.
  • SRP-3586:Log backup overdue alert is being raised wrongly after maintenance window.
  • SRP-1294:The list of SQL processes in an alert does not include the process which caused the alert.

Known issues

  • SRP-495: If the Base Monitor loses its connection to the SQL Monitor Data Repository then you may see the following error, “System.Data.SqlClient.SqlException was thrown by method Query on service DataPresenterService: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding”.
  • SRP-1443: An internal error occurs if the database name contains a non-latin character.
  • SRP-2167: A user will see a “script stack space quota is exhausted” JavaScript error on Firefox when there is a lot of performance data in an alert details page. Use an alternative browser to view SQL Monitor.
  • SRP-2310: “Back in time” can sometime crash with an error when using IE 7. Use an alternative browser to view SQL Monitor.
  • SRP-2702: Long running query process ID not appearing in the SQL Processes/Trace tab.

Didn't find what you were looking for?