Running a job continuously

Dear All,
I would like to have a job that runs all the times, how
should I set up the scheduler ?What does the job do? Do you have a loop so it never finishes? If not, they you cannot have it run
continuous, you can only schedule it very frequently.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Pidgeon" <anonymous@.discussions.microsoft.com> wrote in message
news:0bdc01c4a6fc$76513760$a301280a@.phx.gbl...
> Dear All,
> I would like to have a job that runs all the times, how
> should I set up the scheduler ?
>|||Thanks Tibor
We have a fairly complicated audit procedure where we need
to scan data continuously, I think I will go for your idea
of having a loop that never ends.
I know its a bit of a bad solution but I have been out
voted.
>--Original Message--
>What does the job do? Do you have a loop so it never
finishes? If not, they you cannot have it run
>continuous, you can only schedule it very frequently.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"Pidgeon" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0bdc01c4a6fc$76513760$a301280a@.phx.gbl...
>> Dear All,
>> I would like to have a job that runs all the times, how
>> should I set up the scheduler ?
>>
>
>.
>|||What I do is creating 3 steps in the job. The 1st step runs "EXEC
msdb..sp_purge_jobhistory 'jobname'" to clear the history for this job. The
2nd step runs the procedure and it goes back to step1 on success and step 3
on failure. Step 3 prints out the error report in case the job fails.
"Pidgeon" wrote:
> Dear All,
> I would like to have a job that runs all the times, how
> should I set up the scheduler ?
>
>