Viewing 15 posts - 41,101 through 41,115 (of 59,069 total)
Sorry... post in progress and I accidently hit the "go" buttong too soon...
{edit} Heh... "Buttong!!!!!" Sounds like a high velocity frozen pork chop doing it's job well at...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2009 at 8:30 pm
Alvin Ramard (11/17/2009)
Grant Fritchey (11/17/2009)
Paul White (11/17/2009)
LMGTFY version 2.0:I'm confused now. Shouldn't that be LMBTFY?
Let
Me
Be
The
First
Yeller??
BWAA-HAA!!! You have too much time on your hands, Alvin. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2009 at 5:45 am
... and queries that try to do it all in a single statement... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 16, 2009 at 5:10 pm
All good points (have you got an MS URL that I could read up on or is that info in BOL?). The result is... MAX is a wee bit...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 16, 2009 at 5:52 am
Start with TaskMgr and make sure what's consuming the CPU from the 60,000 ft level, first.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 11:41 pm
Heh... write a stored procedure that takes just one silly little parameter and you suddenly have code that isn't portable between SQL Server and Oracle. True code portability is...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 11:13 pm
lmu92 (11/15/2009)
Now you know why I didn't want to show my function... :crying:
Heh... now you know why I always post mine... someone might improve on it and it's my gain....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 10:33 am
Paul White (11/15/2009)
I'm sure we could even find a way of controlling the task via the Twitter API if we tried!
SHHHH!!! The folks at work might hear you! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 10:30 am
Thanks Adi... it's an old solution and it's not mine. I've just never seen anyone explain it before and thought an explanation was long overdue especially since it's been...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 10:26 am
Heh... I'll say it all "Depends" and managers really need to pay attention to this.
Like Lutz and Kevin, my experience has been that most people just don't know...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 10:17 am
Thanks, Gail. Heh... there goes another myth. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 7:57 am
Almost forgot... even though the CROSS APPLY works well, if you want to shave off another 30-40% on CPU usage, then do the split directly in code instead of using...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 7:52 am
here's the optimizations I was talking about. There are two different types of optimizations... the first one is to reduce the number of concatenations and other calculations as much...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 15, 2009 at 7:16 am
... and the split function is just fine. I've tweeked it with some optimizations over time... I'll be right back to show you...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2009 at 4:45 pm
Well, I didn't post it for three reasons:
Heh... no worries, Lutz. It just struck me as odd because you normally cough up a whole solution. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 14, 2009 at 4:42 pm
Viewing 15 posts - 41,101 through 41,115 (of 59,069 total)