Viewing 15 posts - 41,656 through 41,670 (of 59,067 total)
No problem, Dale. Thanks for the feedback on this and the other post.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 9:37 pm
You bet... thank you for the feedback. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 9:36 pm
Heh... it doesn't matter if anything is bundled or not... you're still going to pay too much. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 9:32 pm
Shoot... I don't fear the maintenance plan wizards. On the contrary... I love them. They help keep me employed by fixing large systems where they've been used unwisely....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 9:22 pm
Wow. The article and the editorial are great but sure could open up pandora's box discussion wise. Without always saying "YES" or getting my nose stuck in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 9:09 pm
And to answer the title of this thread, no, I don't believe there's anyway to do this in SQL Server without some sort of loop whether it's a Cursor, While...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 8:34 pm
Hierarchical code is so ugly in SQL Server. I dislike recursive CTE's even more than a Loop. So here's the loop version. Note that 5, 6, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 8:31 pm
Heh... Never mind, Dale. I just remembered who you are and what you're using the CLR's for.
Like I said... dynamic SQL... unless you want to write another CLR to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 7:43 pm
Yes, it is possible... using dynamic SQL.
What you're going through sounds like a good reason to not use CLR's. What do they do? I ask because there may...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 7:40 pm
Is this what you want?
WITH cteMax AS
(
SELECT ClientID,TestID,MAX(TestDate) AS MaxTextDate
FROM dbo.YourTable
GROUP BY ClientID,TestID
)
SELECT yt.*
FROM dbo.YourTable yt
INNER JOIN cteMax...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 7:39 pm
Jeff Moden (9/16/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 5:05 pm
Dale Burrell (10/3/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 4:50 pm
:Whistling:
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 2:22 pm
To the point of this article, incidental DBA's probably wouldn't use a Tally table even if they knew what it was. The only thing most IDBA's are likely using...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 1:49 pm
Most people don't know about it, but you can also create temporary stored procedures that begin with #.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 12:33 pm
Viewing 15 posts - 41,656 through 41,670 (of 59,067 total)