I am aware of that one, just some people in my shop have told me that is not the preferred way of doing this ...
So according to your local experts, WAITFOR is not the best way to wait for a period of time...
And their reason is?
Do they recommend against using kettles to boil water too?
Well, I suppose you could put a WHILE loop 1 to a few million with a select statement inside. That'll certainly cause a delay....
Or write the whole thing in C# and use it's sleep function. Or call out directly to the Windows API and it's thread suspend (but that could have some horrible side effects)
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass