Job Schedule every 1.5hrs or 90 mins

Question

Post reply

Job Schedule every 1.5hrs or 90 mins

npbhatjee

SSC Enthusiast

Points: 193
More actions
March 25, 2014 at 1:54 am

#289730

Hi everybody,
My questions is in SQL SERVER 2008 R2 ->SQL Server Management Studio -> SQL Server Agent -> Jobs
i have created a job which needs to be executed every 1.5hrs or 90mins.
while creating schedule for this job :
New job Schedule -> Daily Frequency -> (I selected)occurs every:

after focus release from text box time automatically shifted to 60mins
if i select hour(s) and in textbox 1.5
after focus release from text box time automatically shifted to 2 hrs
I need to create a schedule to execute my job every 1.5 hrs or 90mins.
please help me out for this problem....
Thanks and Regards
Niranjan Bhat

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

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

free_mascot One Orange Chip Points: 27164 More actions · Answer 1

It will not take fraction i.e. 1.5 hrs, instead you need to select 90 minutes.

HTH

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."

djj SSCoach Points: 18831 More actions · Answer 2

free_mascot (3/25/2014)
It will not take fraction i.e. 1.5 hrs, instead you need to select 90 minutes.
HTH

That is the problem. He puts in 90 and it changes to 60. I just tried ours and it does the same thing.

homebrew01 SSC Guru Points: 55548 More actions · Answer 3

Same problem here too. Sometimes it changes to 24 minutes, so I have to change it a 2nd time to get it to "stick".

I suppose you could set up a schedule to run every 3 hours starting at 12:00,

and a 2nd schedule to run every 3 hours starting at 1:30.

Silly SQL

I wonder if you could update the system table ? I have not tried it. If you can, it might later get reverted by SQL without you realizing it, so maybe not a good idea.

crmitchell SSCarpal Tunnel Points: 4557 More actions · Answer 4

The other option would be to schedule it every 30 minutes, check last run time and if less than 80 minutes (or some other value slightly less than 90 but greater than 60) ago exit immediately but the two schedules is probably easier.

homebrew01 SSC Guru Points: 55548 More actions · Answer 5

These bugs have been around for a long time. They must be very low on the priority list.

crmitchell SSCarpal Tunnel Points: 4557 More actions · Answer 6

If you were to need a more obscure interval - maybe its an astronomy application and needs to be timed based on the rotation of some planet other than Earth - you could create the job and schedule it to run once.

The final step could then create a new runonce schedule for e.g. 1 hour 13 minutes 6 seconds time.

Note this would be much more flexible but its functionality wouldn't be particularly obvious and a lot more cumbersome to set up so stick with the simpler methods unless you need the added complexity.

free_mascot One Orange Chip Points: 27164 More actions · Answer 7

I have double checked and working fine. I am able to set 90 min. without any issue.

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."