Version 0.23.2111.0 (released: November 19, 2021)

New Features

  • Two new Insight metrics, both giving some assistance in determining how many successful job executions had failed job steps within them. NOTE: a future release will include a report/logging identifying the jobs in question for these metrics.
    • Jobs : Successful Outcome with Failed Steps (Entire History)
    • Jobs : Successful Outcome with Failed Steps (Past 3 Days)

Improvements

  • The License Information tab on the About form now shows the number of days until the expiry of the provided free license.
  • Various UI cosmetic fixes.
  • Removed carriage return and line feed characters from Description and Body columns within Database Mail Items and Database Mail Event Log to prevent cell wrapping of text.

Bug Fixes

  • Exceptions could be thrown if the SQLAI_Preferences.xml file was modified outside of SQL Agent Insight. Default preferences that cannot be loaded are used to mitigate this issue.
■ NOTE
The preferences file should only be modified by SQL Agent Insight itself. Doing so outside of SQL Agent Insight might render the application unusable.
  • System.NullReferenceException: ‘Object reference not set to an instance of an object.’ may occur after closing an Insight. Resolved.
  • The alarms category column on the Dashboard no longer was showing the metric name. This affected versions 0.23.2109.0 and 0.23.2109.50. Resolved.
  • The collection finish time was incorrectly reported in the Insight log.
  • An Insight metric threshold validation may sometimes result in an incorrect severity being applied to a metric, and therefore potentially not issuing notifications.

Version 0.23.2109.50 (released: November 1, 2021)

Improvements

  • Job Conflicts
    • Due to performance improvements in calculating future job execution intervals, jobs that previously ran less than every 5 minutes were not eligible to be charted. This restriction has been modified to jobs with a frequency of less than 1 minute, making them ineligible to be charted. Therefore more jobs will be available for conflict comparisons.

Bug Fixes

  • Job Conflicts
    • In some cases a job might show an incorrect value (a zero) in the frequency column when in fact they met all criteria but didn’t have any conflicts. These jobs are now plottable on the Gantt chart.
    • In some cases a job having a start time the same as a job estimated finish time would result in a conflict resulting in a conflict. This has been resolved.

Version 0.23.2109.0 (released: October 17, 2021)

New Features

  • The project now targets .NET 4.8 Framework, therefore there are new requirements for this version.

Improvements

  • The entire codebase has been converted to C# for ease of future product enhancements.
  • UI Enhancements
    • The Insight form has had a complete overhaul in usability. It is now easier to set thresholds and one can now set individual metrics in maintenance.
      • Previously threshold configuration was done outside of the Insight form and metric maintenance could only be done at a group level. This has been greatly improved in this version.
    • The Insight Configuration dialog has now been simplified as a direct result of the Insight redesign above.
      • In addition, saving of an Insight configuration is automatic.
    • The Preferences dialog has been redesigned for simplicity and options that are no longer relevant have been removed.
    • Controls across forms are now more consistent with one another in functionality, theme and sizing.
    • MDI children forms have been removed, thus the Quick Access Panel is no longer required and has been removed. Instead, forms will show on the users taskbar.
  • Insight
    • One can now access the configuration options of an Insight on loss of communication to the monitored instance.
  • Main
    • Now uses a proper docking manager to manipulate the Available Instances, Previously Connected Instances and Connected Instances panes.
      • Additionally, these pane locations are saved for future runs of SQL Agent Insight.
    • Server names in the Available Instances, Previously Connected Instances, and Connected Instances panes are no longer truncated.
    • Post enumeration of SQL instances, the time for this operation is now included in the completed update message in the status bar.
    • Enumeration of instances on the local network starts immediately instead of waiting for the About dialog to close.
  • Connection
    • The connection dialog will not display if trying to connect to an instance that is already being monitored.
  • Job Monitor
    • The suspend context menu option now allows a direct selection of a time period for quicker suspension of a job.
  • Job History
    • Now refreshes post purging of job history records.
  • Readability. Some grids had data with carriage returns and line feeds therefore making the data unreadable in some cases. Data has been sanitized so that these carriage returns and line feeds have been removed.

Bug Fixes

  • Insight
    • The monitored instance version in the title bar was always showing “RTM” when the version might not necessarily be.
    • The Job Success Rate could have returned an OutOfRangeException on monitoring a brand new instance not having any job history.
    • The Job Success Rate in some cases was not showing the correct value for individual jobs, therefore affecting the overall job success rate in the dashboard.
    • In some cases, the metrics for Proxies were showing as incorrect however, the Proxies form had the correct data.
    • Poor initial display performance from painting all of the controls of individual metrics. This was overcome by the Insight redesign.
    • The value for the metric “MS DB Last Full Backup (Hours)” was staying constant at 99999 (indicating that a backup had not been completed), even though a backup had been completed.
  • Insight Configuration
    • The option to save the settings as the default configuration always named the file at the OS level after the monitored instance name, thus no “default” file was created. In this version, 0.23, there is no longer an option to save as default settings.
  • Dashboard
    • The metrics overview doughnut chart legend rendered at a 1×4 layout when at its minimum size.
  • Connection
    • Multiple connections to the same instance were being allowed if the user specified a port number.
  • Job Monitor
    • Can no longer stop a multi-server job on the master when the job is running.
    • Resolved a cross-thread operation exception thrown post data collection.
    • Exception was being raised when trying to enable or disable an MSX job on a target server.
    • Can no longer attempt to start a job when the agent service is not running.
    • UI fixes on form resizing.
  • Job History
    • Purging of job histories with large data sets should no longer time out.
  • Log Viewer
    • Unhandled exception thrown when the form was closed during the loading of log data.
    • Recorded the incorrect number of agent logs to the Insight log. Reported a value of 1 (one) when there were more logs.
  • Job Conflict Outlook
    • Jobs graphed in the Gantt chart that started at midnight did not show their start time in the tooltip on mouse hover.
  • Preferences
    • If the override application name was set, the option to modify was disabled until the option to override was toggled for a second time.
    • The override application name was not being propagated to all of the monitored instance connections.
  • Main
    • Upon an Insight communication error, the offending monitored instance could not be removed from the Connected SQL Servers pane.
    • Upon showing the first Insight, the Windows notification tray icons status would initially be in a critical state, regardless of the Insight’s underlying state. This could fire email and tray notifications if they were configured.
  • Overall
    • When refreshing some of the forms throughout SQL Agent Insight after a user had selected data, not all resulting grids data was reset, resulting in stale data being shown.