Can SQL Job schedules be used by more than 1 job?

Question

Can SQL Job schedules be used by more than 1 job?

Rod at work

SSC-Dedicated

Points: 34008
More actions
November 22, 2010 at 2:47 pm

#147725

OK, easy, simplistic question here, but I'd like to know the answer anyway. This week, before Thanksgiving (here in the USA) is kind of light, and so I've got a chance to do some work which has been laying around unable to do until now. One of this simple little tasks is a job to clean up some data, which I know can safely be cleaned up (and I've double-checked that with the users). I've just written a simple SQL Job to do the work, and scheduled it to run daily at 6 AM.
The thought occurred to me, is it possible to reuse other schedules which have been defined by other SQL Jobs? It looks to me as though these scheduled times, in SQL Server (at least SQL 2005) are objects unto them themselves. I saw, when scheduling this job to run daily, that there were 2 buttons, one for "New" and the other for "Pick". Just out of curiosity I clicked on the Pick and it showed me all other scheduled "whatever" out there. Those other scheduled "whatever", are they just a schedule, that any job can run by, if it fits the situation? If I have other SQL Jobs that have to run daily at 6 AM, can I just use the schedule that I created for this new SQL Job?
Kindest Regards, Rod Connect with me on LinkedIn.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 1

Yes. And if you change the schedule on one job, you change everyone who's got the same schedule.

I found this only really useful when I needed to do some one-off maintenance things on occassion, and I could simply activate them all at once for a one-shot run at some maintenance hour. Otherwise I wouldn't do this, too hard to realize what-all is connected to the same schedule. It's just as easy to put them all in the same job, 99% of the time.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

WayneS SSC Guru Points: 95460 More actions · Answer 2

Craig Farrell (11/22/2010)
I wouldn't do this, too hard to realize what-all is connected to the same schedule.

Really?

In SSMS, open up a job. In the Job Properties screen, select "Schedules". Click "Pick..." to select existing schedules. In the "Jobs in schedule" column, click the hyperlinked number - the schedule will open and will show you all of the jobs that use that schedule.

Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Links:
For better assistance in answering your questions
Performance Problems
Common date/time routines
Understanding and Using APPLY Part 1 & Part 2

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 3

WayneS (11/22/2010)
Craig Farrell (11/22/2010)
I wouldn't do this, too hard to realize what-all is connected to the same schedule.
Really?
In SSMS, open up a job. In the Job Properties screen, select "Schedules". Click "Pick..." to select existing schedules. In the "Jobs in schedule" column, click the hyperlinked number - the schedule will open and will show you all of the jobs that use that schedule.

Alright, not hard. Just annoying as heck and not something I remember to go doublecheck when I'm repositioning a single job. 😛

Thanks though, you're right, it is *right there*... 'ish.