Viewing 15 posts - 49,576 through 49,590 (of 59,099 total)
pduplessis (6/28/2008)
Jim Russell (6/27/2008)
Jeff -- I am continually amazed at the effort you put in to help us all out. Thanks very much!!
I am with Jim on this one, it...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2008 at 10:40 am
If you change Carl's code to 2000 per customer, you see where Triangular Joins really start to fall apart... time goes up by a factor of 4 for the Triangular...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2008 at 10:36 am
rbamania (6/28/2008)
thanks jeff
Thanks, but Sergiy was first to set you on the right track.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2008 at 10:28 am
rbarryyoung (6/28/2008)
gerald.duncan (6/27/2008)
Very simple. I want to iterate through a directory of flat files and create SQL tables from them. Clear enough?
Actually, no. This is what you are trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2008 at 9:57 am
am (6/28/2008)
Alloc Amt is calculated based on Priority and Alloc Percent from EMPPERCENTTABLE. For EMPID - 1001 and 1002 where priority is 1 so whatever gets paid...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2008 at 9:51 am
SELECT ep.Record,ep.EmpID,r.ReceiptNum,r.Paid,ep.Beg_Balance
FROM EmpPercentTable ep
CROSS JOIN ReceiptsTable r
ORDER BY r.ReceiptNum,ep.EmpID
I'm a bit tired and today's coffee has finally worn off... what formula are...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 11:28 pm
dfalso (6/27/2008)
And to me, I wouldn't presume that 11000 was enough for anything except days since 1970ish.
How many times have you personally needed a Tally table larger than 11,000? 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 11:14 pm
dfalso (6/27/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 10:48 pm
Matt Miller (6/27/2008)
Otherwise - it's very easy to come up with a numbers table of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 10:45 pm
Oh no... about 99% of everything you need to do can be done with a Tally table of 11,000 rows. If you need more than that, you can create...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 7:27 pm
Aye. Thanks for the feedback... I sometimes wonder if posts like that do any good. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 6:36 pm
David Jackson (6/27/2008)
Hats off to Jeff M for teaching us this trickEdit: I see Matt beat me to it, but he is spot on, forget loops if you can.
Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 6:34 pm
Mark (6/27/2008)
But I got errors.
Can't read your mind, Mark... please post the exact text from the errors...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 6:30 pm
zxn001 (6/27/2008)
Ok... so basically when you ask it to opperate a command on a column...
THAT, is the basis of set based programming. THAT, is the necessary paradigm shift necessary...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 6:28 pm
dfalso (6/27/2008)
Also, depending on need, you can adapt the above to dynamic SQL should you want to work with input parameters.
Why would you need to do that?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2008 at 6:25 pm
Viewing 15 posts - 49,576 through 49,590 (of 59,099 total)