Viewing 15 posts - 50,701 through 50,715 (of 59,091 total)
RyanRandall (5/7/2008)
Mark (5/7/2008)
Jeff Marcus (5/7/2008)
If you are using SQL Server 2005 you can use ROW_NUMBER instead.
If you're not using SQL 2005, I guess you could simulate ROW_NUMBER like this...
declare @param...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 10:54 pm
Hugo Kornelis (5/7/2008)
buktseat (5/7/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 10:33 pm
GSquared (5/7/2008)
I've been using Numbers tables for a couple of years now, and I just keep finding more uses for them all the time.
Examples include:...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 10:30 pm
JohnG (5/7/2008)
As for performance testing of various techniques by anyone, I am continually amazed as to the incorrect methods for generating sample data.
Example (taken...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 10:26 pm
GSquared (5/7/2008)
Summary: While the CTE works, and is fast by any normal standard, the Numbers version is even faster, and requires...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 10:15 pm
GSquared (5/7/2008)
Just SP is fine (though I personally dislike the habit - as if anything other than a stored procedure might follow an EXEC keyword). It's SP_ (with an...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 9:59 pm
Carl Federl (5/7/2008)
There are advantages for having the Tally table include 0...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 9:55 pm
Marius Els (5/7/2008)
This is a great example of implementing set-based programming, three thumbs up from me.
Now to apply this to problems going forward!
Thanks for...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 9:44 pm
Mike DiRenzo (5/7/2008)
I look back on all the TSQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 9:41 pm
Carl Federl (5/7/2008)
The first reference for a tally table that I can recall is in "Guide to Sybase and SQL Server" by C. J. Date...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 9:37 pm
chris (5/7/2008)
No need for a tally or temporary tables.
Heres a params example:
DECLARE @Params varchar(8000)
SET @Params...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 9:27 pm
karthikeyan (5/7/2008)
Excellent Article!
It seems that you have written for me at the right time.:) Really, It is very useful for me.
Because so far i have replaced more than 5 cursors...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 8:53 pm
Chirag (5/7/2008)
nice article jeff.Here's another one with more uses of tally table.
http://www.simple-talk.com/sql/t-sql-programming/the-helper-table-workbench/
Thanks for the compliment, Chirag.
Yeah, they do have some neat uses on that particular link. It's very strange...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 8:50 pm
Calvin Lawson (5/7/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 8:38 pm
RyanRandall (5/7/2008)
Nice work, Jeff. That plural table name must've been difficult for you to come to terms with 😀
Heh... it kept me up all bloody night! But "When in...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 7, 2008 at 8:36 pm
Viewing 15 posts - 50,701 through 50,715 (of 59,091 total)