When you open the Add Job wizard, the first section of this wizard requires you to fill general information for the job. You can find the following fields:

• Add/remove Instances - click this option to select the instances where you want to create the job. Click your instances in the Available Instances column and click > to add them to the Selected instances section. You can also use >> to select all available instances.  
• Name - type a name that describes your job or a name that it is easier for you to identify the job with. 
• Owner -  select the owner of this Job. SQL Enterprise Job Manager allows you to select the owner from a list of available users obtained from the instance you have selected before.  
• Category - select a category for your job. For example, you can choose from: Data Collector, Log Shipping, REPL-Alert Response, or others.
• Enable - define if you want your job enabled or disabled. You can create jobs and enable them later. When the job is disabled, the job does not run in response to a schedule or alert. 

• Maintenance mode - enable this option to add a maintenance window in your instance for a job maintenance. For more information, please see below.

  Jobs created in SQL Server Management Studio (SSMS) do not have the option of selecting jobs for Maintenance Mode; however, you can apply it via Edit Job in the SQL Enterprise Job Manager Web Console.

• Description - write a short description of your job to help you identify its objectives, steps, and any other relevant information.

Take into account that you have to specify at least the instance, name, and category in order to create the job. 

How does the Maintenance Mode work?

While SQL Enterprise Job Manager is running the background collecting Service periodically, for every instance it checks if maintenance mode is enabled, if enabled then it checks if the current time falls in between a schedule window for the instance. If it falls in the schedule window then SQL Enterprise Job Manager enables the maintenance mode and sets in_maintenance to 1 in the instance table. In the same way, whenever SQL Enterprise Job Manager is collecting statistics for a given instance, it checks if the instance is in maintenance mode and if the schedule window is expired then it stops the maintenance mode and sets the in_maintenance column to 0 in the instance table.

There are more additional options to enhance the behavior of maintenance mode:

• Disable alerts during maintenance mode - when this selected, SQL Enterprise Job Manager skips new alerts raised in the maintenance mode window.
• Disable non-maintenance jobs during maintenance - when creating a Job via SQL Enterprise Job Manager we have an option to mark a job as in maintenance mode. If this option is selected then all the jobs which are not marked as maintenance mode are disabled at the start of maintenance mode and are re-enabled at the end of the maintenance mode.
• Stop maintenance jobs that run past the maintenance window - if this option is selected, then SQL Enterprise Job Manager sends a trigger to stop the maintenance jobs which are running even after the end of the maintenance mode.

The Maintenance Mode start and stop time might vary because the SQL Enterprise Job Manager Collection Service needs to run at a given time. Because of any delay or network interruption or performance reasons if the collection is delayed then the Maintenance Mode will also start late.

After making your settings in the General section of this wizard, you can finish and save the job, or you can go to any of the following sections: Steps, Schedules, Alerts, Notifications,Targets .