Version 0.24.2205.0 (released: May 29, 2022)
- New functionality via a context menu on the Operators form having the options to:
- Create a new operator.
- Script an operator as Create or Delete.
- Rename an operator.
- Delete an operator.
- Copy a selected operator to a new operator preserving the status, email address, alert notifications and pager settings, all that is required is a new operator name.
- Note that job notifications are not copied since a job can only have one notification operator. This does not override those jobs with this newly copied operator. This is by design.
- Making a selected operator the failsafe operator with notifications via e-mail, pager, or both.
- Double-clicking an existing operator will display and allow modification of its properties.
- New functionality via a context menu on the Job Categories form having the options to:
- Create a new job category.
- Script a job category as Create or Delete.
- Rename a job category.
- Delete a job category.
- Double-clicking an existing job category will display and allow modification of its properties.
- New quick filters, Local and Multiserver, on the Job Categories form.
- New functionality via a context menu on the Schedules form having the options to:
- Create a new schedule.
- Script a schedule as Create or Delete.
- Enable or Disable a schedule.
- Rename a schedule.
- Delete a schedule.
- Double-clicking an existing schedule will display and allow modification of its properties.
- New column in the Schedules form showing the Type of schedule being either, One-time, Daily, Weekly, Monthly, Monthly relative, When SQL Server Agent service starts, or Whenever the CPUs become idle.
- Change all references of Categories to Job Categories for clarity on which type of category is being monitored. SQL Agent Insight does not work with or monitor Operator Categories.
- More logging of actions to the Insight Log for better tracking and visibility of actions taken within SQL Agent Insight.
- Better clarification of the license creation and expiry dates within the About dialog.
- Resolved the error, “String was not recognized as a valid DateTime”, which could have been shown to the user if the client system running SQL Agent Insight had a date format that was incompatible with the format of the expiry date stored in the license file.