Viewing 15 posts - 46,096 through 46,110 (of 59,095 total)
Heh... actually... we're all new here... I learn something new everyday.
Welcome aboard and happy Los Reyes.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 6:26 pm
timothyawiseman (1/6/2009)
Jeff Moden (1/1/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 6:22 pm
Heh... yeah, I've see that before... Funny and nasty all at the same time. 🙂
My concern is that those all say pretty much the same thing... either here's the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 6:13 pm
foxjazz (1/6/2009)
don't you guys have jobs?
Oh hell yes! I'm a professional pork chop launcher! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 6:06 pm
Oh yeah... meant to ask. Barry, do you remember what you did a search on? I did one on the error message itself and got just about everything...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 4:15 pm
Heh... we're running Lotus Notes so not sure any of the servers are running Exchange. I'll take a look, though.
It would really be cool if Barry's suggestion were all...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 4:14 pm
Properly cut pork chops only have 3 sides... well, until they hit... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 4:07 pm
Heh... it's the only way he could get the eyeholes on the helmet right. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 4:03 pm
I agree... there's nothing in the data presented that identifies which row in the first table goes with which row in the second table other than physical order listed... and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 3:57 pm
Crud... I was just reaching for the bucket o' fresh pork chops... 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 3:51 pm
Matt Whitfield (1/6/2009)
Jeff Moden (1/5/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 6:35 am
Grant Fritchey (1/5/2009)
RBarryYoung (1/5/2009)
Actually, I heard from someone at PASS that WITH RECOMPILE does not work reliably for this problem in SQL2005, but "is fixed" in SQL 2008.
WITH RECOMPILE was...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 6:20 am
sqlblue (1/5/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 6:15 am
First, I'd give Peso's code a whirl.
Second, if you really must do the Null conversion to 0, use ISNULL instead of COALESCE... ISNULL is actually quite a bit faster the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 6:05 am
RBarryYoung (1/5/2009)
Jeff Moden (1/1/2009)
Day "0" is 01/01/1900... and it was a Monday... Guess what happens if you add 4 days to any Monday? You get a Friday... every time.
Sorry...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2009 at 5:54 am
Viewing 15 posts - 46,096 through 46,110 (of 59,095 total)