Viewing 15 posts - 41,521 through 41,535 (of 59,067 total)
john.kilgo (10/14/2009)
DECLARE @result varchar(max)
SELECT
@result = coalesce(@result +...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 7:11 pm
Jeff.Mlakar (10/14/2009)
ID NAME
101 Apple
101 Banana
102 Orange
102 Melon
102 Grape
And wanted a result set like:
ID NAMES
101...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 12:51 pm
pmcpherson (10/14/2009)
Fantastic! This forum is making my week! Really! I just have one question now; how do you un-concatenate a string into rows efficiently?
A decent place to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 10:54 am
Joel Mansford (10/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 10:45 am
Adam Haines (10/14/2009)
Actually you dont have replace the invalid characters if you use the FOR XML Clause, with the TYPE directive. You can then use an xquery to extract...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 9:15 am
sdznet (10/14/2009)
the content is very useful.one question-
is it "somewhat" less complex to produce multi-aggregate crosstabs and pivots using ms-access than currently in sql server?
If knowledge about MS-Access were gasoline,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 9:06 am
nicolay.tchernitsky (10/13/2009)
select replace(
convert(
varchar(max),
(select name+',' as [text()] from fruit order...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 2:03 am
Nicely written article but even the optimized solution causes a full cartesian product on the far right of the execution plan. That could explain it's performance problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 1:56 am
Marios Philippopoulos (10/13/2009)
Jeff Moden (10/10/2009)
You don't need a CLR for this...
Thanks, I will certainly take a close look; I just took a quick glance at your article, and it looks...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 14, 2009 at 12:16 am
I noticed you didn't get any replies to your problem. Take a look at the first link in my signature below to see why that might be and what...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 13, 2009 at 7:38 pm
Thanks for the offer, Seth, but in light of the other posts, there's no need unless you can remember the exception you're thinking of. It also seems to me...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 7:39 pm
Great points, George... thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 6:46 pm
Use Lutz's fine example as a derived table and do a join between that and your other column sources. Don't add extra columns to the GROUP BY that are...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 6:39 pm
Garadin (10/12/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 6:33 pm
newbie2009 (10/9/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 12, 2009 at 6:31 pm
Viewing 15 posts - 41,521 through 41,535 (of 59,067 total)