Compartilhar via

sp_delete_job (Transact-SQL)

  • Artigo

Deletes a job.

Syntax

sp_delete_job { [ @job_id = ] job_id | [ @job_name = ] 'job_name' } ,
     [ , [ @originating_server = ] 'server' ] 
     [ , [ @delete_history = ] delete_history ]
     [ , [ @delete_unused_schedule = ] delete_unused_schedule ]

Arguments

  • [ @job_id= ] job_id
    Is the identification number of the job to be deleted. job_idis uniqueidentifier, with a default of NULL.

  • [ @job_name= ] 'job_name'
    Is the name of the job to be deleted. job_name is sysname, with a default of NULL.

    Note

    Either job_id or job_namemust be specified; both cannot be specified.

  • [ @originating_server= ] 'server'
    For internal use.

  • [ @delete_history= ] delete_history
    Specifies whether to delete the history for the job. delete_history is bit, with a default of 1. When delete_history is 1, the job history for the job is deleted. When delete_history is 0, the job history is not deleted.

    Note that when a job is deleted and the history is not deleted, historical information for the job will not display in the SQL Server Agent graphical user interface job history, but the information will still reside in the sysjobhistory table in the msdb database.

  • [ @delete_unused_schedule= ] delete_unused_schedule
    Specifies whether to delete the schedules attached to this job if they are not attached to any other job. delete_unused_schedule is bit, with a default of 1. When delete_unused_schedule is 1, schedules attached to this job are deleted if no other jobs reference the schedule. When delete_unused_schedule is 0, the schedules are not deleted.

Return Code Values

0 (success) or 1 (failure)

Result Sets

None

Remarks

The @originating_server argument is reserved for internal use.

The @delete_unused_schedule argument provides backward compatibility with previous versions of SQL Server by automatically removing schedules that are not attached to any job. Notice that this parameter defaults to the backward-compatible behavior. To retain schedules that are not attached to a job, you must provide the value 0 as the @delete_unused_schedule argument.

SQL Server Management Studio provides an easy, graphical way to manage jobs, and is the recommended way to create and manage the job infrastructure.

This stored procedure cannot delete maintenance plans, and cannot delete jobs that are part of maintenance plans. Instead, use SQL Server Management Studio to delete maintenance plans.

Permissions

By default, members of the sysadmin fixed server role can execute this stored procedure. Other users must be granted one of the following SQL Server Agent fixed database roles in the msdb database:

  • SQLAgentUserRole
  • SQLAgentReaderRole
  • SQLAgentOperatorRole

For details about the permissions of these roles, see SQL Server Agent Fixed Database Roles.

Members of the sysadmin fixed server role can execute sp_delete_job to delete any job. A user that is not a member of the sysadmin fixed server role can only delete jobs owned by that user.

Examples

The following example deletes the job NightlyBackups.

USE msdb ;
GO

EXEC sp_delete_job
    @job_name = N'NightlyBackups' ;
GO

See Also

Reference

sp_add_job (Transact-SQL)
sp_help_job (Transact-SQL)
sp_update_job (Transact-SQL)
System Stored Procedures (Transact-SQL)

Help and Information

Getting SQL Server 2005 Assistance