Viewing 9 posts - 1 through 9 (of 9 total)
Not sure if number of rows matter if this was just for audit purpose I suppose you would not be strict on number of rows.
select * from invoice tablesample (10...
June 9, 2009 at 6:54 am
Agreed that there are much chances of hitting the 1 second window. What I meant was to round of this one second to a perfect second 59 or 00
Anyway adding...
May 11, 2009 at 12:02 am
Agreed there are questions which only MS SQL can answer. That is the reason I left the millis to Application level.
The max we can do to make it most nearest...
May 10, 2009 at 3:19 am
With the rows inserted I found even the orignal function with BETWEEN working same. Inserting the rows in the lookup table can give you desired results but I think we...
May 9, 2009 at 8:48 pm
DateAdd function in MS SQL behaves a little different then what we might want it to. The probability of user getting wrong output because of the milli seconds would be...
May 9, 2009 at 5:29 am
You can evaluate the script, it works very well for me.
April 21, 2009 at 9:34 am
I wonder how did that happened, seems there is some bug with sql server central.
April 20, 2009 at 11:00 pm
check this out. GMT to Local timezone conversions
http://www.sqlservercentral.com/scripts/GMT+conversion/66492/
April 20, 2009 at 10:26 am
I've done something similar too hope you enjoy reading it.
http://www.sqlservercentral.com/scripts/GMT+conversion/66492/
April 20, 2009 at 10:23 am
Viewing 9 posts - 1 through 9 (of 9 total)