Viewing 15 posts - 41,686 through 41,700 (of 59,102 total)
laughingskeptic (10/4/2009)
Jeff Moden (9/22/2009)
That's nice, but let's see you use that in a join or even as a stand-alone result set.
A table valued function will cover this if you don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 5, 2009 at 5:42 am
So, are you all set or do you still need help on this?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 5, 2009 at 5:34 am
Marcin Gol [SQL Server MVP] (10/4/2009)
training kits maybe useful for you too
Only if you actually practice what they teach. Otherwise, you're just memorizing which won't get you anywhere on...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2009 at 9:10 am
The point Seth was trying to make is that if a column in a table doesn't exist but the table does, you'll get an error. Appologies for not following...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2009 at 8:55 am
Garadin (10/2/2009)
These will compile fine if the entire table does not exist. They will not compile if the table exists but the column you're referencing does not. It...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2009 at 9:46 pm
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
Viewing 15 posts - 41,686 through 41,700 (of 59,102 total)