Posted by Matik on 04/27/07 22:04

> to affect this behaviour is about nil. Who knows, maybe there is a trace
> flag, but don't stay up all night looking for it.

I wont :) Have other things to do as well :)

> If you are on SQL 2005, you could write a CLR function which retrieves

I'm on 2000 ... right now ....

> If you are on SQL 2000, you would have to write an extended stored

This is what I was thinking of...

> procedure, which may not be performant enough. (There is quite a cost
> for the eontext switch.)

This is what I was afraid of :(

> But getdate() seems dead in the water when you are living in the fast lane
> like you do.

I just need to change aproach probably, and try to solve it in
different way.
Probably the solution is what I did right now ...
Just, a the beginning, I'm sending procedure to sleep (waitfor delay).
It is not nice, and slows everything down, but maybe ... will be fast
enougth...
Otherwise ... try to do smth. else.

Thanks Erland again for your help and patience.

Best regards

Matik

[Back to original message]