run job schedule evry 20 second HOW

Question

Post reply

run job schedule evry 20 second HOW

midan1

SSCertifiable

Points: 5100
More actions
December 30, 2004 at 1:23 pm

#59879

help
how to run job evry 20 second
thnks ilan

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

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

Phil Parkin SSC Guru Points: 246985 More actions · Answer 1

I cannot schedule anything more frequently than every minute - is that good enough?

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

midan1 SSCertifiable Points: 5100 More actions · Answer 2

no i need it for my web site for live data

any idea how ????????????????

lalibert16 SSC Eights! Points: 928 More actions · Answer 3

Never tried it, but I guess if you shedule 3 jobs that runs each 1 minute with a 20 second difference, it should work.

1st job : starts at 00:00:00 and runs every minute

2nd job : starts at 00:00:20 and runs every minute

3rd job : starts at 00:00:40 and runs every minute

I don't see any other way of doing this.

Eric

midan1 SSCertifiable Points: 5100 More actions · Answer 4

i dont understanding what is the problem of microsoft so thet i can run job evry 20 second ????

no way to manual do it from Transact SQL ????

thnks ilan

noeld SSC Guru Points: 96590 More actions · Answer 5

OK I am going to tell you a little secret use it at your own risk

if you look at sp_add_job schedule the constants defined for the frequency on the parameter @freq_subday_type are

0x1 - Not Used (once a day)

0x4 - Minutes

0x8 - Hours

Do you notice anything missing in that sequence ?.....

Yep, 0x2 should be Seconds so you can script out a job setup with 1 min interval, change the constant and script it back in.

Now, Do you really need this??? you could simply schedule a script out of the server with that pooling interval and execute and sp. That will have the advantage of being supported . On the other hand you will have to make sure that your job is not running next time is called (Jobs are not re-entrant)

HTH

* Noel

midan1 SSCertifiable Points: 5100 More actions · Answer 6

thnks but thre is a problem

----------------------------------

Server: Msg 14295, Level 16, State 1, Procedure sp_verify_jobschedule, Line 57

Frequency Type 0x2 (OnDemand) is no longer supported.

----------------------------------------------

can i to force the JOB to do this

thnks ilan

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 7

Perhaps you could have a stored procedure that runs continuously (loop back to start) with a WAIT DELAY '000:00:20'. That would solve the problem of trying to schedule a job that ran less than once a minute and it would definitely solve the possible reetrant problem.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Steve Jones - SSC Editor SSC Guru Points: 736478 More actions · Answer 8

I like Jeff's suggestion, but I might also add another job to check and be sure the first one is sitll running.