Viewing 15 posts - 41,131 through 41,145 (of 59,102 total)
Matt Miller (#4) (11/17/2009)
Truly awesome solution once again! The rewrite is even better than the original.
...
Just wanted to pass this little redirection to you. ( sorry -...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2009 at 10:52 pm
Weeellllll.... that took a bit (a LOT!!!) longer than I thought. I'll try to get to some of my own testing on some of your contributions tomorrow night.
I've got...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2009 at 10:35 pm
Sorry for the delay in my responses to all of this. Heh⦠you folks look like you had fun without me, though.
Iβll split this response in twoβ¦ first, my...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2009 at 10:27 pm
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
Viewing 15 posts - 41,131 through 41,145 (of 59,102 total)