Viewing 15 posts - 46,411 through 46,425 (of 59,095 total)
RBarryYoung (12/24/2008)
Sandy (12/23/2008)
HAPPY CHRISTMAS & HAPPY NEW YEAR 2009 TO ALL MY SWEETY FRIENDS...(GAIL :), GRANT, STEVE, JEFF, RBAR, & ALL SQL GURUs)
You know I am really not crazy about...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 5:39 pm
Merry Christmas and Happy New Year to you, too, Sandy... and to everyone else, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 5:38 pm
BWAAA-HAAA! Sounds like a heck of a tagline for a new company, Barry 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 5:14 pm
You know... I've never read one of his books... they any good?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 5:10 pm
Sure it can... but then why spend all those brain cells trying to do it in a single query when a proc can do the same thing and maybe a...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 5:04 pm
Matt Whitfield (12/24/2008)
You know what, I have to say - would it kill you to agree with what people have said rather than repeat what other people say and try...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 4:38 pm
Matt Whitfield (12/24/2008)
I tried to test the COALESCE method, but it was horrifically slow over about 10,000 rows. Also interested why you say SELECT COALESCE(@SQL .... when it's actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 4:33 pm
Kurt W. Zimmerman (12/24/2008)
Great post! My view on this is if cursors were so bad then why does the construct even exist? Cursors have their place...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 12:17 pm
What caught my eye was the following...
sognibene (10/23/2008)
I will post what I am able to get working.
That seemed to leave the problem up in the air. I wanted to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 11:51 am
I'm not sure why folks try to use so many bitwise integer columns. It makes the column "multi-purpose" which is not what the definition of a column actually is....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 11:17 am
Wayne West (12/4/2008)
Jeff Moden (11/25/2008)
Wayne West (10/22/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 11:08 am
That's part of the reasoning behind the "forum ettiquette" article that so many of us have in our signature. Lot's of times, just taking that minute or two of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 10:58 am
jacroberts (12/24/2008)
Jeff Moden (12/24/2008)
Good idea, Gaby, and good article...Could you list one thing that's a good idea in this article, spelling mistakes aside?
Nope. I like people who...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 10:46 am
I agree with the other's. Hat's off to Gaby for taking on a highly controversial subject.
As other's have also stated, running DBCC and certain system sprocs is one of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 10:28 am
Phil Parkin (12/23/2008)
And, what order might that be? Order by name, date, extension, 8.3 name, or ???
haha, I was wondering the same and was hoping to draw out the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 24, 2008 at 12:47 am
Viewing 15 posts - 46,411 through 46,425 (of 59,095 total)