Page History

7.5.4 New Features

General

Charts now properly manage real-time and scheduled collection data in the same time span

SQL Diagnostic Manager charts provide data whether collected real time or as part of a scheduled collection event. If you pause or leave this view and then return during the same Console session, SQL Diagnostic Manager displays the real-time data points as previously viewed, followed by a period of data points from any scheduled collections that occurred while you were away. For additional information about how SQL Diagnostic Manager displays charts, see Charts.

Queries

Query Waits now located on Queries tab

The Query Waits feature is no longer located on the Resources tab but now is available on the Queries tab. For additional information about Query Waits, see View Query Waits.

Alerts

Manage how the SQL Diagnostic Manager Console responds to alert notifications

SQL Diagnostic Manager can now play a sound when an event triggers an alert to change states. You can also control how SQL Diagnostic Manager displays the resulting alert notification in the Console. For additional information about Console notifications for alerts, see Configure notification settings.

Set SQL Diagnostic Manager to notify you of only critical alerts

Use the Notifications section of the Console Options feature to set SQL Diagnostic Manager to notify you for only critical alerts. You can select whether you want to view or even play a sound when a critical alert occurs. For additional information about Console notifications for alerts, see Configure notification settings.

Mobile

SQLdm Mobile & IDERA Newsfeed now supports IIS 8

SQLdm Mobile & IDERA Newsfeed now supports IIS 8 on Windows 2012 and Windows 8 environments. For additional information about SQLdm Mobile & IDERA Newsfeed requirements, see SQLDM Mobile and IDERA Newsfeed requirements.

7.5.4 Fixed Issues

General

• SQL Diagnostic Manager now responds to the collection filtering set for disk drives to prevent the Collection service from gathering data on non-monitored disks.
• Users who upgraded to SQL Diagnostic Manager 7.5.3, and who collect data using a direct WMI connection no longer experience an issue causing an instance to stop collecting snapshots.
• An issue causing errors when the Collection service attempted to collect Table Growth information no longer occurs.

Servers

• SQL Diagnostic Manager no longer pauses data point creation in other real-time panels when the user accesses the Timeline view.
• This release fixes an issue caused when the scheduled refresh did not successfully complete, resulting in missing History Browser snapshots.
• The SQL Server Plan Cache object no longer continues to grow with SQL Diagnostic Manager queries even with the SQL Server Optimize for ad hoc workloads server configuration option selected.
• The SQL Diagnostic Manager Powershell plug-in now properly puts monitored SQL Server instances into maintenance mode when selected.

Alerts

• The Autogrow alert no longer displays the same previous and current data file size when viewing alert details in the Alerts view.
• SQL Diagnostic Manager no longer dismisses certain alerts when SQL Diagnostic Manager generates an Unable to Connect, Unable to Monitor, or Paused alerts. These alerts include SQL Server Agent job alerts, VM Host Server Change, VM Resource Configuration Change, Mirroring Server Role Change, and Cluster Failover alerts.
• SQL Diagnostic Manager no longer displays an incorrect percentage in the Database Full (Percent) alert.
• SQL Diagnostic Manager no longer delays generation of some Oldest Open Transaction alerts until the transaction is significantly older than the alert threshold. The alert now triggers immediately when the transaction crosses the threshold.
• An issue preventing some users from monitoring multiple instances and causing job completion error alerts no longer occurs.

Reports

• The Server Summary report now correctly displays statistics graphs and grids even when the results include no data for that interval.
• The Server Statistics report now consistently applies the UTC offset to both servers when using the report to compare two servers.

Counters/Custom Counters

• When WMI counters are unavailable due to a stall, SQL Diagnostic Manager now continues to collect available counter data until it hits the connection limit and triggers an alert.
• VM custom counters now close the connection to the vCenter Server immediately after use, thereby avoiding a high number of connections to the server at one time.

7.5.3 New Features

There are no new features for SQL Diagnostic Manager 7.5.3.

7.5.3 Fixed Issues

General

• Users who upgrade to SQL Diagnostic Manager 7.5.2 no longer experience missed alerts.
• Users who upgrade from SQL Diagnostic Manager 6.2 to a more recent version of SQL Diagnostic Manager no longer experience issues upon subsequent upgrades. SQL Diagnostic Manager displayed the message, "Query Monitor upgrade paused," in the log and caused excessive connections to the Repository.
• Users with large databases who upgrade to SQL Diagnostic Manager 7.5.2 no longer experience Management Service blockage, causing slow inserts into the Repository.
• SQL Diagnostic Manager now successfully installs and no longer stalls on the splash screen while displaying the message, "Connecting to Repository."
• The SQLdm Management Service no longer causes high CPU on the Repository.

7.5.2 New Features

There are no new features for SQL Diagnostic Manager 7.5.2.

7.5.2 Fixed Issues

General

• When upgrading to SQL Diagnostic Manager 7.5.x and a timeout occurs while upgrading the database statistics, SQL Diagnostic Manager now properly re-submits the query and no longer indicates that it is running without re-starting the stopped upgrade. This issue caused some users to not see older database information.
• An issue causing the SQL Diagnostic Manager Console to take a long time to load or time out after upgrading to 7.5 and display the message, "Unable to connect: Timeout expired attempting to open server connection," no longer occurs.
• Users who upgrade to SQL Diagnostic Manager 7.5 no longer experience an issue causing the transaction log file to grow dramatically.
• An issue with the stored procedure p_GetTagServersAsXML not closing or de-allocating a cursor no longer occurs as the stored procedure no longer uses a cursor.
• An issue with table statistics collection causing a communication problem between the Management Service and the Collection Service is resolved.
• SQLdm no longer displays an "Arithmetic overflow error" message when refreshing the Server Summary view This issue was caused by a timestamp containing a value greater than the SQL Server Max Integer value.

Overview

• An issue causing SQL Diagnostic Manager to display some monitored SQL Server instances more than once in the Servers tree no longer occurs.
• The CPU Dashboard panel no longer displays an occasional red "X" in the Call Rates chart when the panel is resized.

Sessions

• SQL Diagnostic Manager no longer displays the messages, "Error executing Session List collector: Arithmetic overflow error converting expression to data type int," or "Error processing Session List Collector: Object reference not set to an instance of an object," when some users attempt to access pages in the Sessions view.

Resources

• SQL Diagnostic Manager no longer displays the error message, "The given key was not present in the dictionary," when a user attempts to view Server Waits.

Alerts

• SQL Diagnostic Manager custom counters now properly trigger alert responses.
• Deadlock and Autogrow alerts no longer persist after the triggering condition is resolved.

Reports

• SQL Diagnostic Manager no longer displays the message, "Item with the same key has already been added," when some users attempt to run the Top tables by Growth or Top Tables by Fragmentation report.
• Users can now select the time of day in all SQL Diagnostic Manager reports by using the Start Hours and End Hours fields.

7.5.1 New Features

There are no new features for SQL Diagnostic Manager 7.5.1.

7.5.1 Fixed Issues

General

• An issue causing an exception error and possibly preventing some users from closing the SQLdm desktop client no longer occurs.

Overview

• The Memory, Network, and Virtualization panel chart selections are now properly saved when a user saves a Dashboard layout.
• Timeline users who double-click an alert to access the Alerts pane with the selected alert highlighted now receive the proper selected alert information in the Details pane of that view.

Sessions

• On a case-sensitive server, the Sessions Blocking graph now shows the correct deadlocks in the sessions.

Resources

• The Query Waits graphs right-click menu options View Text and View Query History are now operative.

Logs

• A user interface update fixed an issue causing some Microsoft Windows 7 users to see a cut-off Search window in the Log tab.

Alerts

• SQL Diagnostic Manager and the Windows Event Log now both show accurate metrics for the OS Disk Free Space (Size) alert.

Reports

• Users who attempt to schedule email notifications for some reports no longer receive an error message at the end of the wizard.
• Generation of the Top Databases report is improved, preventing the report from suffering a time out because of the long load time.
• Disk Details report users no longer receive an exception message when attempting to run the report with the Drive Name field selection of All Drives.

7.5 New Features

There are no new features for SQL Diagnostic Manager 7.5.

7.5 Fixed Issues

General

• The SQL Diagnostic Manager installer no longer checks your Windows firewall service. If you have communication issues after installation, verify that ports 5166 and 5167 are open for access in Windows firewall and/or whichever firewall you use.
• SQL Diagnostic Manager now properly aggregates data based on the number of days displayed in the Aggregate query data into daily records after X days field in the Grooming Options.
• Users monitoring disk activity on Windows 2008 and later operating systems no longer have to wait one second per disk for statistics gathering.
• Users no longer receive false "Unable to connect" alerts for monitored SQL Server instances known to be online. The server availability check now attempts one connection retry in order to avoid alerting in case of transient network issues.
• SQL Diagnostic Manager now can send email notifications to Gmail accounts and other email accounts using SSL encryption.
• The About IDERA SQL Diagnostic Manager dialog box no longer includes the System Info button.

Virtual Machines

• An issue in the SQLdm Management Service causing some VM statistics to not display for monitored virtual SQL Server instances no longer occurs.

Dashboard

• An issue causing the CPU Dashboard panel to display 0 when a greater value should appear no longer occurs. This issue was caused by SQL Diagnostic Manager switching from one counter to another at certain refresh rates when calculating CPU values.

Server Overview

• SQL Diagnostic Manager no longer attempts to delete a monitored SQL Server instance in some situations when the user pressed the Delete key while in the Server view.
• An issue causing some users to receive an exception error when attempting to view Server Details after quickly clicking through different panes of the SQL Diagnostic Manager Management Console no longer occurs.

Sessions

• The Y-axis unit of time measurement now appears in the Sessions > Locks Wait Time chart as "ms" (milliseconds).

Resources

• Resources > Query Waits times are now in chronological order.
• Users no longer receive the error message, "The given key was not present in the dictionary," when attempting to view the Resources > Server Waits view.

Databases

• SQL Diagnostic Manager no longer displays restore activity on the original database instead of the destination database. Now the destination database includes any restore information.

Services

• The SQL Agent Jobs list now retains the open (+) and closed (-) settings after a refresh. This list also remains on the same row after a refresh and no longer jumps to the top of the list.
• An issue causing the job collector to fail for some users no longer occurs. This issue occurred when the user attempted to filter jobs or job categories with a string that included a single quote character (') in the title.

Alerts

• The Alerts pane now retains your column sort selection when you return to the pane after visiting another page, as when investigating an individual alert.
• SQL Diagnostic Manager now sends an alert when a cluster failover occurs even when the server appears as offline in the preceding refresh of the SQLdm Collection Service. Previously, this situation would not trigger a cluster failover alert.
• The Session Tempdb Space Usage (MB) alert now triggers based on the Total User Space Used and no longer includes the Total Internal Space Used in the calculation. This update fixes an issue where users received an alert that shows a tempdb session using more space than the entire size of tempdb.
• The Cluster Failover alert no longer displays a timestamp of 1-1-1900 when an event triggers an alert.
• The Unsubscribed Transactions alert now displays the resulting time in hours, minutes, and seconds for easier comprehension.
• This release fixes an issue that caused some users to receive alerts stating that the data files are over 1000.00% full.
• Users no longer receive multiple email messages for the same alert.

Reports

• Users no longer receive the error message, "An error occurred while retrieving data for this report. Additional information: Invalid Column name. (Microsoft SQL Server, Error: 207)," when attempting to run a custom report.
• An issue causing the Top Queries report to appear empty when the user selected a Custom Range older than seven days no longer occurs.

Custom Counters

• An issue causing some users to receive an error message when attempting to modify an existing custom counter no longer occurs.

7.2.2 New Features

There are no new features for SQL Diagnostic Manager 7.2.2.

7.2.2 Fixed Issues

• SQL Diagnostic Manager 7.2.2 now displays an accurate Physical I/O metric on the Blocking view of the Session tab.
• SQL Diagnostic Manager 7.2.2 no longer displays XML document related error messages to users who upgrade to SQL Diagnostic Manager 7.2 with a SQL 2005 repository. To learn more about the cause of this issue, see Microsoft Support Article 968914, "FIX: When you convert a TEXT column to a VARCHAR(MAX) column, an NTEXT column to a NVARCHAR(MAX) column, or an IMAGE column to a VARBINARY(MAX) column, the original NULL values in these columns may become empty strings in SQL Server 2005."
• An issue causing some users to receive an error message when attempting to view details for a monitored SQL Server instance no longer occurs. When this issue occurred, the results were replaced by a large red X.
• Both the Alerts and Custom Area views in SQLdm Mobile now display your custom counters regardless of whether you defined unique category names. By default, SQL Diagnostic Manager assigns the category “Custom” to all custom counters.

7.2.1 New Features

SQL Server 2012 RTM Support

SQL Diagnostic Manager 7.2.1 supports the use of SQL Server 2012 RTM version. Users who implement the SQL Server 2012 AlwaysOn functionality should note that while SQL Diagnostic Manager seamlessly monitors servers with this feature enabled, it does not currently administer or diagnose issues with AlwaysOn.

7.2.1 Fixed Issues

• Users who have implemented SQL Diagnostic Manager 7.2 with SQL Server 2012 RC0 in a non-production environment may experience issues with data display on the Tempdb Summary and Database Files views after upgrading to SQL Diagnostic Manager 7.2.1. Upgrading to SQL Server 2012 RTM their test environment will remedy this issue.
• SQL Diagnostic Manager 7.2.1 no longer displays error messages related to an "XML document" when users who upgraded to SQLdm 7.2 attempt to access the SQLdm Management Console.
• Users who implemented SQL Diagnostic Manager 7.2 with SQL Server 2012 RC0 in a non-production environment now receive an accurate name and version number for SQL Server 2012 RTM when viewing the Compatibility Level for a monitored SQL Server 2012 RTM instance.

7.2 New Features

Monitoring SQL Server virtual environments

Get complete insight into the performance of your virtualized SQL Server databases. Monitor and track VMware-specific performance counters allowing you to get a complete performance picture of the SQL Server environment. Two VM-related reports provide performance trends and a summary of your virtualized environment. For additional information about configuring the new VM functionality, see Configure your virtual machine connections.

SQL Server 2012 experimental support

SQL Diagnostic Manager 7.2 is SQL Server 2012 RC0 compatible. This version of SQL Diagnostic Manager is not certified against newer builds of SQL Server and should not be used with these builds in a production environment. IDERA provides experimental support while you use your installation in a testing environment to ensure the features you rely on most are working as or better than expected.

Users who implement the SQL Server 2012 AlwaysOn functionality should note that while SQL Diagnostic Manager seamlessly monitors servers with this feature enabled, it does not currently administer or diagnose issues with AlwaysOn. For additional information about SQL Diagnostic Manager and SQL Server 2012, see SQL Diagnostic Manager requirements.

SQLdm Mobile views

SQLdm Mobile features a new server dashboard specifically for tablets and incorporated VMware monitoring data. For additional information about the new SQLdm Mobile features, see SQLdm Mobile Help.

Reporting on Tempdb Statistics

You can now run the Tempdb Statistics report to quickly identify and keep tabs on tempdb performance-related issues. For additional information about the new tempdb report, see Tempdb Statistics report.

SQL Server Memory Usage Percent counter available for custom reports

You can now select the SQL Server Memory Usage Percent counter when creating a custom report. For additional information about creating a custom report, see Custom reports.

Updated alert notification functionality

SQL Diagnostic Manager now allows you to suppress system tray notifications when a monitored SQL Server instance returns to an OK status. Click Tools > Console Options. On the Notifications tab, check the Never show console alert notifications when the server status goes to OK checkbox, and then click OK. For additional information about the Management Console options, see Configure Console Options.

CPU Statistics report now available in a custom range of hours

The CPU Statistics report now includes an option for you to select a custom date range and view results in hours. To select this range, click Reports > CPU Statistics. Select the appropriate monitored SQL Server instance, and then select Custom Range from the Period drop-down list. Use the calendar tool to select the range, and then click OK. Select Hours from the Sample drop-down list to view your results in hours. For additional information about the CPU Statistics report, see CPU Statistics report.

Input how long SQL Diagnostic Manager waits before raising an alert for a long-running job

Users can now specify a minimum job length for the SQL Server Agent Long Running Job (Percent) alert. This may be used to prevent alerting on short or trivial jobs. For additional information about configuring job exclusions, see Configure Job Exclusions.

7.2 Fixed Issues

• Users with a large number of databases no longer notice a performance issue caused by leaving the SQL Diagnostic Manager Dashboard open for a long period of time.
• The Value Configuration window in SQL Diagnostic Manager no longer displays blank column headings but includes alert state icons to easily identify the content. You can access the Value Configuration window by clicking Edit on the Alert Configuration window.
• The Login Time column of the Sessions Details page now uses the local time on the client server for the timestamp. You can access the Sessions Details page by clicking Sessions > Details while viewing a monitored SQL Server instance.
• SQL Diagnostic Manager no longer displays an error message when a user attempts to view tempdb detail for a SQL Server 2000 monitored instance. Tempdb monitoring is supported for SQL Server 2005 and above monitored instances only.
• Table growth collection no longer fails for monitored SQL Server 2000 servers, allowing the Top Table Growth report to function correctly.
• SQL Diagnostic Manager no longer displays an error message when a user attempts to use PowerShell cmdlets to configure Query Monitor.
• The CLR Enabled alert now properly functions after triggering an Informational alert.
• The Export to Excel function on the Tempdb Sessions view no longer fails for users who had cells in the Last Command column containing more that 32,767 characters.
• The Database Statistics report results format is updated and no longer causes any issues in viewing accurate results for users with large databases.
• SQL Diagnostic Manager no longer displays and error message when a user attempts to schedule an email delivery of the Top Tables by Fragmentation report.
• The Repository now properly saves Query Monitor data while the grooming job runs.
• A failure in the SQL Diagnostic Manager replication monitoring no longer prevents otherwise successful scheduled refreshes from saving to the repository.
• The Table Fragmentation (Percent) alert now changes to gray shading if the alert is raised for more than 12 hours.
• Extremely long queries no longer cause the Query Monitor to generate OutOfMemory exceptions on the Collection Service. These exceptions could previously cause a service crash.
• Users no longer experience an error during installation that caused an error when attempting to validate the user account used to perform the install.
• Performance updates including query aggregation and grooming changes improve SQL Diagnostic Manager data collection and processing efficiency.
• SQL Server authentication no longer occasionally fails for users attempting to use a password containing the quotation mark (") special character.
• When you delete a database, the system is groomed to removes all references to that database. Now the feature also grooms the deleted database from the [SQLServerDatabaseNames] table.

7.1.1 New Features

There are no new features for SQL Diagnostic Manager 7.1.1.

7.1.1 Fixed Issues

• Improvements now allow SQL Diagnostic Manager to return data for the Session Details page more quickly and avoid a timeout due to slow or no response.

7.1 New Features

New SQL Server dashboard

SQL Diagnostic Manager now features a completely redesigned dashboard, which dramatically expands the display of your performance data and simplifies the view of the overall health of a SQL Server instance. For additional information about the new dashboard, see the SQL Server performance overview.

New Tempdb monitoring

You can now quickly identify and resolve tempdb performance-related issues with the new tempdb monitoring and diagnostic views. For additional information about the new tempdb monitoring functionality, see tempdb status summary.

New SQLdm Mobile views

The following new views in SQLdm Mobile make diagnosing performance issues even easier while you're on the go:

• • Blocking Chain View
  • Sessions > Top Wait Customer View
  • Tempdb Monitoring View

For additional information about SQLdm Mobile, see SQLdm Mobile Help.

View and copy SQL Agent Job messages from the Job History list

SQL Diagnostic Manager now allows users to view SQL Agent Job messages from the Job History list. Right-click the appropriate job, and then select View Message. A copy feature allows you to copy the existing message and then paste it into a different application. For more information about SQL Agent jobs, see how to Monitor SQL Agent Jobs.

7.1 Fixed Issues

• SQL Diagnostic Manager Repository timeouts no longer cause the SQL Diagnostic Manager services to stop for some users.
• This release of SQL Diagnostic Manager fixes an issue that caused SQL Diagnostic Manager to display an error message when some users attempted to configure alerts.
• SQL Diagnostic Manager performance improvements decrease the amount of time spent waiting for page loading and processes to complete.
• The CLR Enabled alert now properly retains settings when the user changes the alert state to Informational.
• SQL Diagnostic Manager no longer experiences an issue when a user adds servers to a custom view.
• Improved collection functionality corrects an issue causing some users to see an incorrect SQL CPU Usage statistic.
• Refreshing the SQL Agent Jobs view no longer deselects all selected rows.
• The SQLdm Service Availability chart on the Services tab no longer incorrectly displays, "Unable to monitor" when the server is available.
• SQL Diagnostic Manager no longer displays an error message when users who upgrade to SQL Diagnostic Manager 7.0 attempt to edit their custom counters.
• SQL Diagnostic Manager no longer displays the error message, "An INSERT EXEC statement cannot be nested," for some users who attempt to run a report when SQLdm Application Security is enabled.
• SQL Diagnostic Manager users monitoring SQL Server instances by IP address instead of name no longer receive the error message, "The server you are trying to access is not monitored by IDERA SQL Diagnostic Manager," when attempting to view history for a mirrored database.
• Users who have clustered servers no longer receive the error message, "Error interpreting Services Collector: Invalid length parameter passed to the substring function" when attempting to use the Show Real Time View function.

7.0 New Features

New SQLdm Mobile interface

SQL Diagnostic Manager now offers a Web application (SQLdm Mobile) that displays real-time SQL Server performance dashboards on a variety of mobile devices, including iPhone, iPad, Android and Blackberry. SQLdm Mobile includes the IDERA Newsfeed technology. The IDERA Newsfeed is a revolutionary new way for DBAs and managers to collaborate, share knowledge, and keep close tabs on their most critical SQL Server issues.

New Alert Templates

SQL Diagnostic Manager now offers alert templates, which allow a user to configure generic alert settings to apply to monitored SQL Servers or groups of servers all at once. You can create and assign alert templates to any of your monitored SQL server instances.

New Informational Alerts

Informational alerts allow you to set a threshold that triggers a status that does not affect the overall status of the server within SQL Diagnostic Manager. You can use informational alerts to notify an administrator of the state of a particular metric for a server or trigger secondary processes that could take action to prevent issue escalation.

Improved Alert Response Usability

Alert Response rules, which configure how SQL Diagnostic Manager responds when an event triggers an alert, are easier to create and manage due to an updated interface and process. Users can now apply an alert response rule to all metrics quickly and easily.

Improved Notification Times for Unresponsive SQL Server Instances

SQL Diagnostic Manager can now alert you more quickly when one of your monitored SQL Server instances becomes unresponsive for any reason. Although the default is set to 30 seconds, you can adjust the interval at which the Collection Service checks whether your SQL Server instances are “up” or available. If a connection is not confirmed within the specified time, SQL Diagnostic Manager creates an Unable to Connect alert.

Improved Metrics Collection

The Collection Service now:

• • Uses a different SQL Server metric to determine the CPU Busy Value for instances running SQL Server 2005 or later. This change prevents timeout errors during the metric collection process.
  • Uses separate processes to collect table growth and fragmentation metrics. This approach ensures quiet time data collection does not delay alerts about other metric thresholds.
  • Is able to efficiently collect error log metrics for SQL logs that are large or infrequently cycled.

Improved Repository Performance

The SQL Diagnostic Manager Repository database will perform more efficiently due to the following enhancements:

• • The Repository grooming job now:
    • Calls the index maintenance in a separate step. Using SQL Server Management Studio, you can now disable this step and then later run your own index maintenance script after the grooming job completes.
    • Better handles I/O and CPU demands when processing data.
  • Several stored procedures used by SQL Diagnostic Manager Repository were updated.

New Reports

SQL Diagnostic Manager now offers the following new reports:

• • The Metric Thresholds report is for users who want to view a list of metric thresholds for a monitored SQL Server instance. The report includes the metric name, description, and threshold for their informational, warning, and critical alerts.
  • The Disk Details report lists key disk metrics for a specific SQL Server instance. This report offers Disk Time Per Read, Disk time Per Transfer, Disk Time Per Write, Disk Reads Per Second, Disk Transfers Per Second, and Disk Writes Per Second.

7.0 Fixed Issues

Alerting Updates

SQL Diagnostic Manager now offers the following updates to alerting:

• • SQL Diagnostic Manager now accesses the correct database when a user double-clicks an associated Fragmentation alert on the Active Alerts tab of the SQLdm Today page. When you use this feature, SQL Diagnostic Manager displays the affected database information on the Tables & Indexes pane of the Databases tab.
  • Editing an alert response no longer causes SQL Diagnostic Manager to display an error message when attempting to save your changes. This issue affected users who manually changed XML detail in the repository, and then attempted to save additional alert response changes using the SQL Diagnostic Manager Console.
  • SQL Diagnostic Manager now properly captures customer error detail when Error: 0, Severity: 19, State: 0 occurs. This issue affected users using the SQL Server error log alert.
  • The SQL Diagnostic Manager scheduled alert refresh is no longer dependent on table statistics before completing a full refresh and possibly triggering alerts. Because table growth and fragmentation can be long-running processes, SQL Diagnostic Manager was delayed in delivering alerts. These items were removed from the scheduled alert refresh for a more responsive alert system.
  • SQL Diagnostic Manager now raises an alert when a monitored SQL Server instance does not respond within the default 30 seconds. You can configure the response time in the Server Properties.
  • SQL Diagnostic Manager now checks to make sure that the WMI services are running before trying to connect to a monitored SQL Server instance. If SQL Diagnostic Manager detects that previous attempts to connect are causing multiple connections, it will stop monitoring that server and triggers an alert. All real time views in SQL Diagnostic Manager will display an error message explaining the issue. SQL Diagnostic Manager automatically resumes monitoring once the number of connections drops below the default of 30 connections.

Fragmentation Monitoring Updates

SQLdm now offers the following updates to your table fragmentation monitoring:

• • SQLdm now accurately collects table fragmentation data on tables within the entered size range. An issue causing SQLdm to collect table fragmentation data on tables less than the entered minimum size no longer occurs.
  • Large tables no longer cause a block when collecting table fragmentation on a monitored SQL Server instance. This issue occurred when multiple very large tables were involved. Fragmentation data for populating the reorganization panel on all tables in a database is not collected. The reorganization query in SQLdm 6.1 and SQLdm 6.2 can timeout before table statistics are collected. For more information, refer to IDERA Solution 1583.

SQL Server Statistics Updates

SQL Diagnostic Manager now offers the following updates to the functionality that collects and analyzes your SQL Server statistics:

• • The Sessions view now retains any custom filtering when viewing your Historical Snapshots. Custom filtering across all snapshots helps you quickly determine changes needing your attention.
  • The History Browser on the Queries tab now allows you to scroll when you have large amounts of data.
  • The SQL Server Physical I/O chart on the Resources tab now displays values in seconds instead of raw values. Displaying results in seconds provides you with more accurate real-time analysis.
  • Users with mirrored databases no longer receive an error message that the mirror is not monitored when the database is actually monitored. This issue affected users viewing their monitored mirrored database information in the real time view on the Mirroring pane of the Databases tab.
  • SQL Diagnostic Manager now includes a new counter for collecting CPU stats. This new counter include a number of improvements over the previous counter, which occasionally suffered an error due to reaching maximum capacity cumulative CPU time.
  • SQL Diagnostic Manager no longer displays an error message when a user stops the Session Detail Trace and then refreshes the view. Previously, users received the error message, "Error starting Session Details collector System.InvalidOperationException: BeginExecuteReader: CommandText property has not been initialized."
  • Users with very large numbers of tables no longer cause the CPU to reach maximum threshold during table statistics collection. New processes allow SQL Diagnostic Manager to read large data sets in smaller chunks to avoid collecting unnecessary data and causing a strain on CPU resources.
  • Users working on diagnostics while troubleshooting can now add a configuration file entry to limit the procedure cache row count. The new key is maxRowCountProcedureCache, which has a default value of 10000.
  • This release includes improvements to the repository grooming process, which fixes grooming of the ServerActivity table and resolves an issue causing occasional deadlocks during grooming.

Reporting Updates

SQL Diagnostic Manager now offers the following updates to reporting:

• • Unauthorized users can no longer access data for restricted SQL Server instances when viewing a report through SQL Server Reporting Services. This issue affected all users who restrict access to specific instances using Application Security features. This update improves data security and prevents confusion when a user unwittingly views data for the wrong instance.
  • Users can now select up to 10 Windows, SQL Server, and/or custom counters when creating a custom report. These additional counters provide more flexibility and detail in your reports.
  • If a custom counter contains special characters (<>%-), then your custom report generation fails with the error: Field names must be CLS-compliant identifiers. A CLS-compliant Custom Counter name uses the following rule: the first character of an identifier can be an uppercase or lowercase, titlecase, modifier, or other letter, or letter number. The subsequent characters can be any of the previously-mentioned characters, plus non-spacing or spacing combining marks, decimal numbers, connector punctuation, and formatting codes.