SQLJobCommander:ReleaseNotes: Difference between revisions
From Brentec I.T. Solutions
More actions
| Line 10: | Line 10: | ||
* Should a job monitor connection to an instance fail, the status of the SQL agent is not updated appropriately. | * Should a job monitor connection to an instance fail, the status of the SQL agent is not updated appropriately. | ||
* When creating or editing a job, the same schedule can be chosen more than once. However, on save, duplicate schedules are removed. | * When creating or editing a job, the same schedule can be chosen more than once. However, on save, duplicate schedules are removed. | ||
* There is no immediate indication of an error should one happen while copying a job to another instance. However, the error is output to the session log. | |||
Revision as of 21:27, 22 July 2026
Home | Download from the MS Store | Download from Brentec | Features/Visual Tour | Requirements | Documentation | Change Log | Roadmap
Version 0.1.2606.0 (June 14, 2026)
- Initial release! Enjoy!
- See what SQL Job Commander can do for you over in the documentation.
Known Issues
- Should a job monitor connection to an instance fail, the status of the SQL agent is not updated appropriately.
- When creating or editing a job, the same schedule can be chosen more than once. However, on save, duplicate schedules are removed.
- There is no immediate indication of an error should one happen while copying a job to another instance. However, the error is output to the session log.