Viewing 15 posts - 50,836 through 50,850 (of 59,091 total)
Heh... no problems there, Ryan... it'll generate a million rows very quickly for performance testing, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 9:09 am
Although the last problem is correct, I can tell you that whoever wrote the test is probably looking for the outer join solution instead of the where not exists solution....
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 8:48 am
You've already got one... Books Online 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 8:41 am
First, you might want to try asking your Oracle question on an Oracle forum... you'll usually get more correct answers that way... just a thought. 😉
Second, Oracle requires you to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 8:40 am
Here's a demo of what you can do in cases like this in both SQL Server 2000 and 2005... test data included...
--drop table jbmtest
--===== Create and populate a 1000 row...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 8:34 am
Having one of those "where's my porkchops and slingshot" days, Grant? 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 8:25 am
Personally, I don't allow developers to have write access to anything in production... violates all sorts of merchant agreements and PCI standards not to mention a total lack of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 8:20 am
Thanks, Barry... I've never heard of anyone else calling such aggregations a "Tally Table", but I certainly can see where the term both applies and is convenient.
Just to throw another...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:41 am
You don't actually need a numbered column using the TOP (XX) methods... just need a good set of indexes and the correct "sort".
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:25 am
Ok... thanks... just trying to figure it all out... I think that's the last piece. I'll see what I can do tonight.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:18 am
Grant Fritchey (5/1/2008)
Oops. Modulo 3.:blush:
Heh... I've done the exact same thing... start thinking "Quarters", start writing "4's" 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:15 am
rbarryyoung (4/30/2008)
Jeff Moden (4/30/2008)
I'm curious... Why 4 months? That's a third of a year...
That's probabrly why, Jeff. I did some work for an insurance company several years ago...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2008 at 6:14 am
I'm curious... Why 4 months? That's a third of a year...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2008 at 10:53 pm
I found it... it's not as robust as I thought it was, but it does have several pieces of test code along with some reasons why some works better than...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2008 at 10:37 pm
Nice job, Lynn!
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2008 at 10:22 pm
Viewing 15 posts - 50,836 through 50,850 (of 59,091 total)