Stop a Job

Applies to: SQL Server Azure SQL Managed Instance


On Azure SQL Managed Instance, most, but not all SQL Server Agent features are currently supported. See Azure SQL Managed Instance T-SQL differences from SQL Server for details.

This topic describes how to stop a Microsoft SQL Server Agent job. A job is a specified series of actions that SQL Server Agent performs.

Before You Begin

Limitations and Restrictions

  • If a job is currently executing a step of type CmdExec or PowerShell, the process that is being run (for example, MyProgram.exe) is forced to end prematurely. This can cause unpredictable behavior, such as files that are being used by the process being held open.

  • For a multiserver job, a STOP instruction for the job is posted to all target servers of the job.


For detailed information, see Implement SQL Server Agent Security.

Using SQL Server Management Studio

To stop 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 stop, and then click Stop Job.

  3. If you want to stop multiple jobs, right-click Job Activity Monitor, and then click View Job Activity. In the Job Activity Monitor, select the jobs you want to stop, right-click your selection, and then click Stop Jobs.

Using Transact-SQL

To stop a job

  1. In Object Explorer, connect to an instance of Database Engine.

  2. On the Standard bar, click New Query.

  3. Copy and paste the following example into the query window and click Execute.

    -- stops a job named Weekly Sales Data Backup  
    USE msdb ;  
    EXEC dbo.sp_stop_job  
        N'Weekly Sales Data Backup' ;  

For more information, see sp_stop_job (Transact-SQL).

Using SQL Server Management Objects

To stop a job

Call the Stop method of the Job class by using a programming language that you choose, such as Visual Basic, Visual C#, or PowerShell. For more information, see SQL Server Management Objects (SMO).