|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
simulate infinite loopHello everyone,
I would like to run a select statement every nine seconds 24 hours a day, 7 days a week, 365 days a year unless I physically stop the select statement myself. Currently I have a while loop that runs 89 or 90 times with a wait for command in it to select information into a table in a stored procedure that I set up a job for. The job runs every 14 minutes. However, during backup execution the stored procedure runs slow and that causes a time lapse in my job. I'd like to learn about any suggestions anyone might have. Thanks, Chieko Consider scheduling this as a SQL Server job.
Show quote "chieko" <chi***@discussions.microsoft.com> wrote in message news:E1BA09E6-4C09-4AAE-A807-B79F2B3024CC@microsoft.com... > Hello everyone, > I would like to run a select statement every nine seconds 24 hours a day, > 7 days a week, > 365 days a year unless I physically stop the select statement myself. > Currently I have a while loop that runs 89 or 90 times with a wait for > command in it to select information into a table in a stored procedure > that I > set up a job for. The job runs every 14 minutes. However, during backup > execution the stored procedure runs slow and that causes a time lapse in > my > job. > I'd like to learn about any suggestions anyone might have. > Thanks, > Chieko yup. already did that. its a job that occurs every 14 minutes. but if the
while loop lasts even a second more than 14 minutes, then the job waits an additional 14 minutes before it repeats and I lose information. Chieko Show quote "JT" wrote: > Consider scheduling this as a SQL Server job. > > "chieko" <chi***@discussions.microsoft.com> wrote in message > news:E1BA09E6-4C09-4AAE-A807-B79F2B3024CC@microsoft.com... > > Hello everyone, > > I would like to run a select statement every nine seconds 24 hours a day, > > 7 days a week, > > 365 days a year unless I physically stop the select statement myself. > > Currently I have a while loop that runs 89 or 90 times with a wait for > > command in it to select information into a table in a stored procedure > > that I > > set up a job for. The job runs every 14 minutes. However, during backup > > execution the stored procedure runs slow and that causes a time lapse in > > my > > job. > > I'd like to learn about any suggestions anyone might have. > > Thanks, > > Chieko > > > You can set up the job to run every 9 sec instead. Here is the
demonstration: http://www.sqldev.net/sqlagent/SQLAgentRecuringJobsInSecs.htm -- Anith That should work.
Thanks, I would never have found it by myself. Chieko Show quote "Anith Sen" wrote: > You can set up the job to run every 9 sec instead. Here is the > demonstration: > http://www.sqldev.net/sqlagent/SQLAgentRecuringJobsInSecs.htm > > -- > Anith > > > It looks like the smallest time interval is only 10 seconds. Is there a way
to over ride this so that i can run it every 9 seconds? Show quote "chieko" wrote: > That should work. > Thanks, I would never have found it by myself. > Chieko > > "Anith Sen" wrote: > > > You can set up the job to run every 9 sec instead. Here is the > > demonstration: > > http://www.sqldev.net/sqlagent/SQLAgentRecuringJobsInSecs.htm > > > > -- > > Anith > > > > > >  |
|||||||||||||||||||||||
Other interesting topics