Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Automatically Delete a Job
Collapse the table of content
Expand the table of content

Automatically Delete a Job


This topic describes how to configure Microsoft SQL Server Agent in SQL Server 2016 to automatically delete jobs when they succeed, fail, or complete by using SQL Server Management Studio or SQL Server Management Objects.

Job responses ensure that database administrators know when jobs complete and how frequently they run. Typical job responses include:

  • Notifying the operator by using e-mail, electronic paging, or a net send message.

    Use one of these job responses if the operator must perform a follow-up action. For example, if a backup job completes successfully, the operator must be notified to remove the backup tape and store it in a safe location.

  • Writing an event message to the Windows application log.

    You can use this response only for failed jobs.

  • Automatically deleting the job.

    Use this job response if you are certain that you do not need to rerun this job.

In This Topic

To automatically delete a job

  1. In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.

  2. Expand SQL Server Agent, expand Jobs, right-click the job you want to edit, and then click Properties.

  3. Select the Notifications page.

  4. Check Automatically delete job, and choose one of the following:

    • Click When the job succeeds to delete the job status when it has completed successfully.

    • Click When the job fails to delete the job when it has completed unsuccessfully.

    • Click When the job completes to delete the job regardless of completion status.

Arrow icon used with Back to Top linkBookmark link 'Top' is broken in topic '{"project_id":"7d6ffa79-2ddc-4606-b774-a6a5d46784cd","entity_id":"92dbb6da-5919-4bde-9354-d454e9ea3da0","entity_type":"Article","locale":"en-US"}'. Rebuilding the topic '{"project_id":"7d6ffa79-2ddc-4606-b774-a6a5d46784cd","entity_id":"92dbb6da-5919-4bde-9354-d454e9ea3da0","entity_type":"Article","locale":"en-US"}' may solve the problem.

Community Additions

© 2015 Microsoft