Create a Schedule

You can create a schedule for SQL Server Agent jobs in SQL Server 2016 by using SQL Server
Management Studio, Transact-SQL, or SQL Server Management Objects.

Before you begin:

Security

To create a schedule, using:

SQL Server Management Studio

Transact-SQL

SQL Server Management Objects

Before You Begin

Security

For detailed information, see Implement SQL Server Agent Security.

Using SQL Server Management Studio

To create a schedule

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

2. Expand SQL Server Agent, right-click Jobs, and select Manage Schedules.

3. In the Manage Schedules dialog box, click New.

4. In the Name box, type a name for the new schedule.

5. If you do not want the schedule to take effect immediately after it has been created, clear
the Enabled check box.

6. For Schedule Type, select one of the following:

o To start the job when the CPUs reach an idle condition, click Start whenever the
CPUs become idle.
 o If you want a schedule to run repeatedly, click Recurring. To set the recurring
schedule, complete the Frequency, Daily Frequency, and Duration groups on
the dialog.

o If you want the schedule to run only one time, click One time. To set the One
time schedule, complete the One-time occurrence group on the dialog box.

Using Transact-SQL
To create a schedule

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.

4. -- creates a schedule named RunOnce.

5. -- The schedule runs one time, at 23:30 on the day that the schedule is
created.
6. USE msdb ;
7. GO
8.
9. EXEC dbo.sp_add_schedule
10. @schedule_name = N'RunOnce',
11. @freq_type = 1,
12. @active_start_time = 233000 ;
13.
14. GO

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

Using SQL Server Management Objects

To create a schedule

Use the JobSchedule 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).