Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Anton Shepelev Newsgroups: comp.databases.ms-sqlserver Subject: Alternative to WAITFOR DELAY Date: Wed, 29 Nov 2017 23:38:36 +0300 Organization: A noiseless patient Spider Lines: 13 Message-ID: <20171129233836.16edaac99510193c72857910@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Injection-Info: reader02.eternal-september.org; posting-host="85cc17ee4445131a3e1c31a0d6153f8b"; logging-data="994"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19j16fV8ttNF0kiuDtSjQBpPgL3mlZQDXU=" X-Newsreader: Sylpheed 3.5.0 (GTK+ 2.24.23; i686-pc-mingw32) Cancel-Lock: sha1:vDghNWwMsrRJLLtL4zEnagjuFRo= Xref: csiph.com comp.databases.ms-sqlserver:1998 Hello, all Is there a more granular way to ease a tight polling loop in T-SQL than WAITFOR DEALAY? A delay of 3.33 milliseconds being a tad too long for my purposes, I seek a way to implement delays of about half a mil- lisecond or shorter. I do not need the precision of real-time systems and will accept any solution to prevent a fast WHILE 1=1 loop from hogging the CPU. -- () ascii ribbon campaign -- against html e-mail /\ http://preview.tinyurl.com/qcy6mjc [archived]