Change the Scheduling Details for a SQL Server Agent Master Job
Applies to: SQL Server Azure SQL Managed Instance
Important
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 change the scheduling details for a job definition in SQL Server by using SQL Server Management Studio or Transact-SQL.
Before You Begin
Limitations and Restrictions
A SQL Server Agent master job cannot be targeted at both local and remote servers.
Warning
It is possible to attach multiple jobs to the same schedule. Note that updating a schedule will impact all the jobs attached to the schedule.
Security
Permissions
Unless you are a member of the sysadmin fixed server role, you can only modify jobs that you own. For detailed information, see Implement SQL Server Agent Security.
Using SQL Server Management Studio
To change the scheduling details for a job definition
In Object Explorer, click the plus sign to expand the server that contains the job whose schedule you want to edit.
Click the plus sign to expand SQL Server Agent.
Click the plus sign to expand the Jobs folder.
Right-click the job whose schedule you want to edit and select Properties.
In the Job Properties -job_name dialog box, under Select a page, select Schedules. For more information on the available options on this page, see Job Properties - New Job (Schedules Page).
When finished, click OK.
Using Transact-SQL
To change the scheduling details for a job definition
In Object Explorer, connect to an instance of Database Engine.
On the Standard bar, click New Query.
Copy and paste the following example into the query window and click Execute.
-- changes the enabled status of the NightlyJobs schedule to 0 -- and sets the owner to terrid. USE msdb ; GO EXEC dbo.sp_update_schedule @name = 'NightlyJobs', @enabled = 0, @owner_login_name = 'terrid' ; GO
For more information, see sp_update_schedule (Transact-SQL).
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for