Viewing 15 posts - 51,391 through 51,405 (of 59,091 total)
SQL ORACLE (3/31/2008)
We can use BIT MASK concept to implement this task.
Sure could... now, pretend it's 5PM on a Friday and you have a really hot gig at 5:30PM (what...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:21 pm
The only thing that can be faster than the Tally Table is Dynamic SQL... but that's not a split and it does have some security issues if it's public facing.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:09 pm
escaleraroyal (3/31/2008)
They just asked me to performance tune it.
But it appears the SP insert data if (party_data) > 36. Then it adds up a sort_order, and for new instrument_id the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:06 pm
GSquared (3/3/2008)
Just did some tests.The XML version is faster, significantly so, than the Numbers table version, for parsing out a string.
Any bets? 😉 Post your test data please, the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 9:39 pm
ksullivan (3/30/2008)
What you want to do is not directly possible.
Heh... not quite true... 😉 And the Tally Table method always wins the race when it comes to this...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 9:34 pm
CROSS APPLY = CORRELATED SUBQUERY
CORRELATED SUBQUERY = RBAR
RBAR + UDF + TABLE VARIABLE = S....L....O....W
Heh... Lowell!!! :blink: You of all people should know that the Tally Table method...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 9:03 pm
Adam Haines (3/31/2008)
A pretty good source is w3schools. This site offers lots of differnent tutorials and practices, with easy to understand examples.
Yeah... just remember... that's not T-SQL... and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 8:05 pm
Buxton69 (3/31/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 8:00 pm
Matt Miller (3/31/2008)
Jeff Moden (3/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 7:52 pm
srienstr (3/31/2008)
Daniel Wilson (5/22/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 7:39 pm
Thanks John G... and spot on... the hard part most certainly is getting developers and designers to think in correct set based frames of mind... Sometimes that even includes SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 7:33 pm
Wayne West (3/31/2008)
I agree, performance isn't as big of a deal as it was back in 4.x/6.5 days.
Perfect... everyone keep thinking that way... keeps me employed fixing performance problems...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 7:24 pm
rbarryyoung (3/30/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 7:18 pm
Robert (3/31/2008)
Considering the level of the question, I wouldn't think so either. However, when dealing with customers or assisting fellows developers on...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 7:06 pm
Buxton69 (3/31/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 7:03 pm
Viewing 15 posts - 51,391 through 51,405 (of 59,091 total)