Viewing 15 posts - 35,716 through 35,730 (of 59,099 total)
Harveysburger (12/10/2010)
SELECT [Month] = DATENAME(mm, DATEADD(mm, MONTH(SomeDateTime), 0)), Amount = SUM(SomeAmount)
FROM #MyHead
WHERE SomeDateTime...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2010 at 8:13 pm
BTW... the problem with the first two queries (after the test data setup) is that they both have full blown Triangular Joins in them.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2010 at 8:10 pm
david.soussan (12/10/2010)
Well Dave, I was hoping for some real benchmark data, but thanks anyway.
Setup SQL Profiler and you'll have it. 😉
So far as true portability across platforms goes, it's a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2010 at 7:45 pm
Hardy21 (12/7/2010)
Sachin Nandanwar (12/7/2010)
Jeff Moden (12/4/2010)
Sachin Nandanwar (12/3/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2010 at 7:27 pm
LOOKUP_BI-756009 (12/9/2010)
SELECT DISTINCT A.Status
FROM dbo.Test1 A
LEFT JOIN dbo.Test2 B
ON A.Status= B.Status
WHEREB.Status IS NULL
AND A.Status IS NOT NULL
Number of rows in dbo.Test1 A = 150 000
Number of rows in dbo.Test2 B...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2010 at 6:28 pm
WayneS (12/11/2010)
Jeff Moden (12/11/2010)
Try this...I knew there was a simpler way, but I just couldn't figure it out. Thanks Jeff!
Thanks for the feedback, Wayne. Hmmmm... one "spackle" article coming...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2010 at 10:28 am
BSavoie (12/11/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2010 at 10:27 am
Try this...
--===== Define the desired dates for a reservation
DECLARE @StartDate DATETIME,
@EndDate DATETIME;
SELECT @StartDate = '2011-02-07',
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 9:29 pm
Jeff Moden (12/11/2010)
Eralper (12/2/2010)
But if you are using cursors instead of CTEs, then that will not be a performance optimized option.
In most cases of recursive CTE's, I've actually found the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 5:01 pm
Abhijit More (12/2/2010)
Is there is any way to break / avoid the recursion in the CTE QUERY??
No. If you could explain a bit more of what you're actually trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 4:26 pm
Eralper (12/2/2010)
But if you are using cursors instead of CTEs, then that will not be a performance optimized option.
In most cases of recursive CTE's, I've actually found the WHILE loop...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 4:24 pm
This should do it compliments of some old but very reliable mag tape methods I learned in the 50's 😉 No need for an extra table, either.
WITH
cteGroupedDates AS
( --===...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 4:13 pm
CELKO (12/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 4:09 pm
CELKO (12/8/2010)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 2:56 pm
Just a personal opinion here... I don't believe in such canned tests because they're not testing for what I want to see in a Developer or DBA.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2010 at 2:38 pm
Viewing 15 posts - 35,716 through 35,730 (of 59,099 total)