BOL mentions this: WAITFOR { DELAY 'time' | TIME 'time' }
But, using this stmt I can only control hours:minutes:secs where as I want
to be able to go into milliseconds.
Any ideas ?
TIA,
-- Shashank
WAITFOR DELAY '00:00:00.100'
Note that SQL Server datetime values are only accurate to about 3
milliseconds.
--
Hope this helps.
Dan Guzman
SQL Server MVP
-----------------------
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
-----------------------
"Shashank Date" <sd...@everestkc.net> wrote in message
news:d68d85c03fa777d4...@news.teranews.com...
Aw, c'mon didn't you even experiment :-)
select current_timestamp
go
WAITFOR DELAY '00:00:00:997'
go
select current_timestamp
go
Heck, I didn't know this before either ;-)
BPM
"Shashank Date" <sd...@everestkc.net> wrote in message news:d68d85c03fa777d4...@news.teranews.com...
Never thought about it <sheepish grin>
> WAITFOR DELAY '00:00:00:997'
Well, like Dan says values are only accurate to about 3 millisecs.
I noticed that you can use both '00:00:00:997' colon and '00:00:00.997'
dot before the millisecs.
So is this one of those "undocumented features" ?
To be used with caution then !
Thanks
-- Shashank
"Dan Guzman" <dang...@nospam-earthlink.net>
> So is this one of those "undocumented features" ?
> To be used with caution then !
Not sure about that. It's certainly not documented by example, but the documentation does say:
'time'
Is the amount of time to wait. time can be specified in one of the acceptable formats for datetime data
which makes me think that it is documented.
I doubt that we'll be able to pin Microsoft down on this, tho' :-)
BPM
"Shashank Date" <sd...@everestkc.net> wrote in message news:33d76d4738129aab...@news.teranews.com...