Home/ Questions/Q 8278115
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T08:53:58+00:00

MY PROBLEM(scenario): There is a already a built in method call WAITFOR that can

  • 0

MY PROBLEM(scenario):

There is a already a built in method call “WAITFOR” that can make the execution of a for example a “Stored Procedure”. This waiting can only be done for less than 24 hours.

But the thing is my client who is also a developer wants to find a method to go around this issue and find a way to wait more than 24 hours to reduce the development time.

There is already a method. That can query necessary tables once a day and send the necessary emails to the customers ect..

I know that since this “WAITFOR” is limited to 24 hours, There has to be a performance issue as this number of “WAITFOR” executions go higher (For example 2000).

MY QUESTION:

  1. Is there a way of holding a stored procedure more than 24 hours. Lets say for more than 14 days.
  2. If there is not a method to work this out,,How should I defend on this issue, What are the facts that I can give to my client, Such as Performance Issues,,

This is what I think,,
Since this waiting is limited to 24 hours is that there is no other option to give the expected functionality to perform a data base task precisely on time. But this gives a big over head to the server to keep the track of each “WAITFOR” execution. If this is more than 2000 or so,, This is impossible to bear for the server.

The best option available is to have a “SQL Agent Job” that run once a day(as you wish) and get the values that are related to set the WAITFOR to execute some job precisely on time.

Please give me a much better understanding on this issue of waiting for more than 24 hours. To go for the next alternative. :((((

Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Is there a way of holding a stored procedure more than 24 hours. Lets
    say for more than 14 days.

    Yes, 14 x 24 hour WAITFOR‘s for example .. but of course that would be terrible beyond all ability to describe; you are forcing a connection to remain open for that period, consuming resources on the server for that period and so on.

    What you describe is precisely what an SQL Agent Job is for, use one.

    • 0