SQL Agent Job ran outside of schedule

Question

SQL Agent Job ran outside of schedule

jboudinot

Mr or Mrs. 500

Points: 558
More actions
September 10, 2010 at 8:21 am

#387764

I have a SQL Agent Job that ran last night (9/9/2010) @ 2300. The schedule is a daily recurring schedule with the occurrence set for 2300, the only problem is that the start date is 8/2/2010 and the end date is 8/4/2010. I'm not sure why it randomly decided to execute last night.
Here is an excerpt from the job history: The Job was invoked by Schedule 31 (DBIS0022 SCHEDULE).
Below are the contents of sysschedules as they relate to Schedule 31:
schedule_id: 31
schedule_uid: 54D496F4-3735-41D8-9496-578EA049776A
originating_server_id: 0
name: DBIS0022 SCHEDULE
owner_sid: 0x0105000000000005150000006C6EFB743C4CAC0F0A25256E28840200
enabled: 1
freq_type: 4
freq_interval: 1
freq_subday_type: 1
freq_subday_interval: 0
freq_relative_interval: 0
freq_recurrence_factor: 0
active_start_date: 20100802
active_end_date: 20100804
active_start_time: 230000
active_end_time: 235959
date_created: 2010-05-07 09:29:28.607
date_modified: 2010-08-02 08:13:52.437
version_number: 8
Any thoughts would be greatly appreciated!

Viewing 7 posts - 1 through 6 (of 6 total)

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

crazy4sql SSCoach Points: 19590 More actions · Answer 1

Have you checked the job might be configured in some other job as znother step. Not necessarrily to same server but could be calling this job from another server.

----------
Ashish

jboudinot Mr or Mrs. 500 Points: 558 More actions · Answer 2

I'd wondered if someone had accidentally ran it or it was kicked off by another job or something, but the history specifically says it was invoked by that schedule.

crazy4sql SSCoach Points: 19590 More actions · Answer 3

i dont think history give you information on either the job was called from some other server's job step or its own step.

----------
Ashish

jboudinot Mr or Mrs. 500 Points: 558 More actions · Answer 4

If the job is kicked off from another job, the history says it was invoked by our SQL Agent account, not the job schedule.

jboudinot Mr or Mrs. 500 Points: 558 More actions · Answer 5

This job decided to run again last night, we still haven't figured out how it is starting. Thanks for your ideas.

jboudinot Mr or Mrs. 500 Points: 558 More actions · Answer 6

Figured out that this is happening after the nodes change in the cluster. Not sure why that's causing it yet though.