Viewing 15 posts - 52,651 through 52,665 (of 59,072 total)
Perfect... another "convert" to denounce the evils of RBAR 😛
Thanks, for the feedback, Whitt. Real glad we could collectively make such a difference for you.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2008 at 6:52 pm
Tony McGarry (2/6/2008)
I doesn't generate unnecessary numbers and is easy to understand
[font="Courier New"]CREATE FUNCTION dbo.GetSequence
(
@Start BIGINT,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2008 at 6:31 pm
How in the world did you get parallel execution out of it? I've tried it on both a 4 CPU and an 8 CPU SQL 2k SP4 installation and...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2008 at 6:14 pm
Thanks for the retest, John 🙂
Sure... Matt and I go round'n'round... it's all in good nature and we both learn things in the process. Hopefully, everyone both understands that...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2008 at 6:09 pm
GSquared (2/6/2008)
Yes, if you for some reason need to create a list of sequential numbers on...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2008 at 7:33 am
Very nicely done, Jacob.
Please... not trying to take anything away from this great article... just sharing a different method...
As a slightly easier to remember (and, a bit faster, too) approach...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2008 at 7:13 am
Sorry James,
It's a "numbers" table that consists of nothing but a column of well indexed sequential numbers. Matt, Peter (Peso), and a lot of the others know about it....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2008 at 5:45 am
I pretty much agree with Matt... yeah, I'm all about speed and performance... but only when I've done job #1 which is to protect the data at any and all...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2008 at 5:48 pm
Nice job, Bill.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2008 at 5:42 pm
rdijk (2/5/2008)
isn't this a little easier??CREATE Function GetMonthEnd(@Date DateTime)
Returns DateTime
AS
RETURN dateadd(d,(day(@date)) * -1,@date)
END
Heh... only when you actually make it return the correct answer 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2008 at 4:12 pm
I got this example from Sergiy... it totally changed my mind about the use of Float. Pay particular attention to the difference between the 3rd and 4th column in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2008 at 3:59 pm
If the process has the correct criteria to keep rows from being updated more than once, then you could SET ROWCOUNT 1000000 and loop until @@ROWCOUNT returns zero...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2008 at 3:35 pm
It IS a cool solution... Wasn't so good in the performance department on my machine, though... it took 29 minutes to do the million row example on my machine... correlated...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2008 at 3:30 pm
You bet, Toni. Thanks for all the feedback code you took the time to write and test. Everone learns something new when good folks, like yourself, do just...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2008 at 12:55 pm
Roger that... heh, yeah, ran into the NVARCHAR thing you speak of which, of course, didn't work worth a hoot. Pretty much squared away, now. Thanks again for...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2008 at 12:38 pm
Viewing 15 posts - 52,651 through 52,665 (of 59,072 total)