Comments on: SQL SERVER – Time Delay While Running T-SQL Query – WAITFOR Introduction http://blog.sqlauthority.com/2009/01/03/sql-server-time-delay-while-running-t-sql-query-waitfor-introduction/ Notes of a SQL Server MVP and Database Administrator Sat, 21 Nov 2009 05:54:09 +0000 http://wordpress.com/ hourly 1 By: Rick Sline http://blog.sqlauthority.com/2009/01/03/sql-server-time-delay-while-running-t-sql-query-waitfor-introduction/#comment-53921 Rick Sline Tue, 21 Jul 2009 13:54:06 +0000 http://blog.sqlauthority.com/?p=1947#comment-53921 Some years ago I could not get a job scheduled through the server (politics) and had to launch a mission critical application that was all in T-SQL every day at the later of: 1) 5am 2) when a particular record was written to a table each day. On "bad' days this could be as late as 7 or 8am I didn't want to keep hitting the server in a tight loop, so I'd leave the SP running to fire at 5am to check for the record, I'd then re-check every 10 minutes. As an aside, if "the record" wasn't in place by 6am I'd normally be on the phone to the person responsible for that process to see what the hold-up was. for major delays I'd cancel the job until I got the all-clear. Some years ago I could not get a job scheduled through the server (politics) and had to launch a mission critical application that was all in T-SQL every day at the later of:
1) 5am
2) when a particular record was written to a table each day. On “bad’ days this could be as late as 7 or 8am

I didn’t want to keep hitting the server in a tight loop, so I’d leave the SP running to fire at 5am to check for the record, I’d then re-check every 10 minutes.

As an aside, if “the record” wasn’t in place by 6am I’d normally be on the phone to the person responsible for that process to see what the hold-up was. for major delays I’d cancel the job until I got the all-clear.

]]> By: michael oneill http://blog.sqlauthority.com/2009/01/03/sql-server-time-delay-while-running-t-sql-query-waitfor-introduction/#comment-45582 michael oneill Tue, 13 Jan 2009 16:33:29 +0000 http://blog.sqlauthority.com/?p=1947#comment-45582 hi, I use the WAITFOR command allot in DTS's while an External Application (WinRar) compacts Access MDB files that have just been created from SQL Views. Once the Delay has timed out I then publish the Zipped files to our website. The WAITFOR command saved me creating lots of different DTS or Batch files can kicking then off at different times. Cheers Michael hi,
I use the WAITFOR command allot in DTS’s while an External Application (WinRar) compacts Access MDB files that have just been created from SQL Views. Once the Delay has timed out I then publish the Zipped files to our website. The WAITFOR command saved me creating lots of different DTS or Batch files can kicking then off at different times.
Cheers Michael

]]> By: Dena http://blog.sqlauthority.com/2009/01/03/sql-server-time-delay-while-running-t-sql-query-waitfor-introduction/#comment-45406 Dena Tue, 06 Jan 2009 13:55:43 +0000 http://blog.sqlauthority.com/?p=1947#comment-45406 We have the use for a waitfor due to our developers writing a process that returns a status code. We will give it 45 seconds, check the results and continue depending on the results. We have the use for a waitfor due to our developers writing a process that returns a status code. We will give it 45 seconds, check the results and continue depending on the results.

]]> By: Josh http://blog.sqlauthority.com/2009/01/03/sql-server-time-delay-while-running-t-sql-query-waitfor-introduction/#comment-45318 Josh Sat, 03 Jan 2009 21:21:02 +0000 http://blog.sqlauthority.com/?p=1947#comment-45318 I have the same questions as John. I understand the value of the first example to wait X seconds until doing something else, but I don't get why you would wait until a specific time to execute. Why not use SQL Agent with a scheduled job? I assume that second feature simply exists, but that best practices would be to use an agent job? Is the benefit perhaps for a one time or semi-random AdHoc style situation? Also how does it handle waiting for a specific time to execute? Does it check in the background and thus consume resources the entire time it is waiting for the specified date/time or does it have a more efficient way of "sleeping" until it is needed? I have the same questions as John.

I understand the value of the first example to wait X seconds until doing something else, but I don’t get why you would wait until a specific time to execute.

Why not use SQL Agent with a scheduled job?

I assume that second feature simply exists, but that best practices would be to use an agent job?

Is the benefit perhaps for a one time or semi-random AdHoc style situation?

Also how does it handle waiting for a specific time to execute?

Does it check in the background and thus consume resources the entire time it is waiting for the specified date/time or does it have a more efficient way of “sleeping” until it is needed?

]]> By: John http://blog.sqlauthority.com/2009/01/03/sql-server-time-delay-while-running-t-sql-query-waitfor-introduction/#comment-45311 John Sat, 03 Jan 2009 11:49:56 +0000 http://blog.sqlauthority.com/?p=1947#comment-45311 Have you ever used WAITFOR in a production environment? I've never really seen much of a use for it and I'd be interested to hear ideas of practical uses for it. For any situations where I want to delay the start of a query (e.g. DBCC commands run outside of core business hours), I've always used SQL Server Agent instead. Have you ever used WAITFOR in a production environment?

I’ve never really seen much of a use for it and I’d be interested to hear ideas of practical uses for it.

For any situations where I want to delay the start of a query (e.g. DBCC commands run outside of core business hours), I’ve always used SQL Server Agent instead.

]]>