Known issues in version 1.0

Installation

• SQL Enterprise Job Manager may prompt to close other IDERA products such as SQLdm or SQLsafe for its uninstall process.   

General

• When the server running SQL Enterprise Job Manager is rebooted, users may find that  the SQL Enterprise Job Manager Collection service has not started and an error message will be displayed indicating that the service is not running.

Adding/Editing Jobs

• This first version provides the most important functionality to create/edit SQL Server jobs. Users should take into account that some options, like job step types (“SQL Server Analysis Services Command” or “SQL Server Integration Services Package” for example) that are handled by SQL Server Management Studio, may not be present in the current version of SQL Enterprise Job Manager.  
• Users may find that when they switch views after they reschedule jobs in the Schedule tab, the changes in the rescheduled job will not be updated in the calendar until the collector runs or they manually refresh the data.
• Users will not be able to edit jobs with names that contain characters such as “&” and “+”.  Additionally, users should take into account that jobs with names that include ‘ and “ characters, may not be allowed to edit these jobs or will be prompted with an error message when trying to edit them.   

• Any selection made to multiple items across SQL Enterprise Job Manager lists (jobs, instances, and alert rules) will be lost when sorting, filtering, refreshing, moving through pages, or performing other actions on the same section. 

• On the Schedule tab when users double click a time slot to create a new job, SQL Enterprise Job Manager currently does not display the job created in the selected time slot. It takes into account the time slot selected, and according to the time zone difference between instance and calendar, it displays in the calendar the time slot that would correspond to that time in the instance. For example, if the time zone of the computer where SQL Enterprise Job Manager is running is at UTC-6 and the instance where the user chooses to create a job  is at UTC-8 time zone, when the user double clicks the 7:00 pm time slot to create a job, the following outcomes should be expected:

• • The job will be created at 7:00 pm on the selected instance
  • The Schedule tab will take into account the time zone difference between instance and calendar and will display the job 9:00 pm.

SQL Enterprise Job Manager monitors and manages your SQL Server agent jobs. Learn more > >