Viewing 15 posts - 50,056 through 50,070 (of 59,102 total)
If you notice, there's a (6) footnote marker... The style with the "Z" is valid only when converting from VARCHAR to DATETIME... not when converting DATETIME to VARCHAR. Dunno...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 10:54 pm
Like RockMoose did... no cursor... no loop... no RBAR from UDF usage. Slightly different take though... for ,, I return a Null... for , , I return a blank.
Borrowing...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 10:41 pm
Tech_Newbie (6/13/2008)
If...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 9:40 pm
Correct... the DATETIME datatype has a resolution of 3.3 milliseconds.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 9:31 pm
I'd sure be willing to try if you'd post your distance function, the CREATE TABLE statements for the two tables, and attach the data for all 25 stores and a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 9:25 pm
sharma (6/13/2008)
I had created a .fmt file
It shows error as invalid column number.
How...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 9:02 pm
It might be a little bit slower than a whole bunch of math, but it sure is simple thanks to STR...
DECLARE @FloatDateTime FLOAT
SET @FloatDateTime = 20080613023001...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 8:53 pm
I wouldn't worry about how long it takes to create the initial space. The important part is that you create as large a piece as you think you'll need...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 8:25 pm
It's one of the most frequently asked questions, ever... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 8:18 pm
Basically, you cannot convert it into true setbased code. Sure, you can probably get rid of all the looping by concatenating all of the commands into one huge variable...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 8:13 pm
Thanks for the feedback, Kevin... and thanks for the code you posted. There are only a few people who will take the time to actually do performance tests never...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 7:41 pm
Kevin Rathgeber (6/13/2008)
So using more real world scenarios, the while always seems to win out though not by much.Jeff, does this seem right to you?
I'd pretty much agree depending on...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 6:49 pm
Ok... lemme demonstrate a couple of things... first, we need some data that everyone
can use and we need lot's of it because these tests run so darned fast. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 6:14 pm
Well, welcome aboard, Kevin! "Set-based" is nothing more than processing sets of information instead of processing "Row By Agonizing Row" (other wise known as "RBAR"... see my tag line...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 2:46 pm
Outstanding, Kevin! Thanks for posting the code.
Yep, Matt was right... One test is worth a thousand words... let the "test off" begin. To make it easier for...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2008 at 2:24 pm
Viewing 15 posts - 50,056 through 50,070 (of 59,102 total)