Viewing 15 posts - 46,681 through 46,695 (of 59,101 total)
Actually, if you do a search for "Numbers Table", you'll find all manner of methods to make such a "tableless" number generator. I don't use them... I use an...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 6:32 am
sabarichandru (12/11/2008)
Hi jeff,thanks for your kind gesture .
could u reveal the logic behind the Query you sent .
Thanks in Advance!
Regards,
Sabari.C
Basically, it's nothing more than a bunch of "derived tables"...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:52 am
Sergiy (12/10/2008)
Jeff, I know, you've got SQL2k5 to play with, but this is SQL2k forum, remember?😉
Crud... nah... I missed that... I was just flying through some posts and didn't look....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:46 am
rite2shubhra (12/10/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:42 am
Zeev Kazhdan (12/11/2008)
All I want to put City and State information in front of Project
means for me that all the calculations should be done for the group of those...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:40 am
johncyriac (12/10/2008)
Have a look at Tally/Number Table methods also
Sure... got any links? 😉 And, how do they apply for this particular problem?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:37 am
Nope... no style wars... I'm just tired of people blaming it on the ability to comment out rows easier. The difference between the two styles only affects the ease...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:30 am
Heh... that bit of info should be as a comment in the code. 😉
Anyway, works good.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:19 am
I also don't see anything that would prevent "overruns"... what happens if you use 1001 of any given sequence? Either BOOM or duplication.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:15 am
Be very careful... There is nothing there that will keep 2 or more simultaneous calls to the same code from returning the same number.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2008 at 5:02 am
Sure, but as others have already stated, a table source for this is the best way to go. The following code will solve the problem without a table, though....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 9:42 pm
Post the OSQL command, please.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 9:24 pm
EAV won't be a slow as you think. It'll process about 12 million rows in about 7 seconds.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 9:05 pm
halifaxdal (12/10/2008)
Here is my task:
I have couple records marked as integrity = 1 or 2 or 3 or 4
I need to write a query to pull out all...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 8:58 pm
Heh... I hate it when impatient people pull this crap... this is a double post... please, no more answers on this thread... go to the following, instead...
http://www.sqlservercentral.com/Forums/Post.aspx?SessionID=gjq2tn3letp4qj554vsxeizy
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2008 at 8:55 pm
Viewing 15 posts - 46,681 through 46,695 (of 59,101 total)