Viewing 15 posts - 44,101 through 44,115 (of 59,101 total)
I've been very disappointed with every outsourcing venture we've had, so far. Examples include such things as code that has UDF's that call 4 levels of UDF's and things...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2009 at 9:58 am
RBarryYoung (4/22/2009)
WayneS: yeah, what Jeff said. Sorry 🙂
Heh... no need to be sorry... it's a very common typing mistake that I occasionally make myself. The names are...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2009 at 9:51 am
Try Master.sys.SYScolumns instead... it contains at least 11,000 rows which will produce up to 121 million rows with a single cross-join. And, although it looks fine, double cross joins...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2009 at 12:03 am
Thanks, Manie. I sure do appreciate the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 11:57 pm
Bob Hovious (4/21/2009)
This beast features double-barelled carburetors.... errrr tally tables.... one with two columns, and nested CROSS APPLYs.
Can you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 11:16 pm
Milovan Banicevic (4/21/2009)
Can I achieve same result WITH NO CURSOR applied???
Absolutely... see the following article (Look for "One final split trick")...
http://www.sqlservercentral.com/articles/TSQL/62867/
... and the following post where many, many different solutions...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 11:12 pm
Paul White (4/21/2009)
On first look, the performance improvement is down to the QO choosing a much more sensible plan when a VARCHAR is used, rather than a MAX datatype....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 5:10 pm
David Burrows (4/21/2009)
Maybe someday, I can teach Jeff something.
Me too, I await that day also :w00t:
Like I've told others, I learn something new from each thread I read. I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 11:20 am
Hey, Steve... do they send you any kind of notification if an abstract for PASS has been accepted? And, considering things like agressive spam filters, is there a place...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 11:14 am
Edward Boyle (4/20/2009)
My strings usually have less that 20 "tokens"
Edward.... first, please understand that I'm absolutely NOT trying to be a wise guy here...
I've found that many folks use the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 10:02 am
RBarryYoung (4/21/2009)
However, in my experience there are three factors that are not well...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 9:52 am
Phil Factor (4/21/2009)
http://www.sqlservercentral.com/Forums/FindPost696606.aspx
Thanks, Phil.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 9:49 am
Phil Factor (4/21/2009)
For the particular string-splitting function, then the WHILE loop, and the Quirky Update solutions, behave predictably and linearly.
Sorry Phil... Haven't been able to keep up on this thread...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 21, 2009 at 5:35 am
Peter, don't be as bad as the cause. 😉 Lots of us got mad at him for all the name calling. And, the etymology of the word...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2009 at 11:16 pm
Matt Whitfield (4/20/2009)
But - I have to say it - I can't think of a way of getting round bruce.t's problem - which I personally found really disappointing!
I may...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2009 at 9:08 pm
Viewing 15 posts - 44,101 through 44,115 (of 59,101 total)