Viewing 15 posts - 41,551 through 41,565 (of 59,102 total)
P Jones (10/15/2009)
BTW if it's kilt Wednesday at Pass who's entitled to wear which tartan?Hunting Stewart for Jeff Moden, master of the Pork Chop weapon?
Heh... two things no one...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2009 at 9:05 am
Elliott W (10/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2009 at 8:59 am
Rob Fisk (10/15/2009)
I did a wee compare last night but do not have the results due to a bit of a power...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2009 at 8:02 am
Rob Fisk (10/15/2009)
in the example above, coalesce is used to remove NULL entries.
The below works just the same using that example:
DECLARE @Name AS varchar(Max);
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2009 at 7:40 am
Andy DBA (10/14/2009)
Jeff Moden
--Jeff Moden
Change is inevitable... Change for the better is not.
October 15, 2009 at 7:35 am
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
Viewing 15 posts - 41,551 through 41,565 (of 59,102 total)