Viewing 15 posts - 51,391 through 51,405 (of 59,098 total)
rbarryyoung (4/1/2008)
And as far as I'm concerned, IN and EXISTS OK to use. They are just as fast as Joins when used correctly and greatly aid code clarity.
WHERE IN...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 5:35 am
Heh... I'm thinking that's more than two options right there 😉 Lets see... DTS, OSQL query, SP_OA* sprocs... there's a couple more, but I forget.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 11:58 pm
Yes... don't use either... use an INNER JOIN instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 11:47 pm
Extract into what? Are the files all in the same format? We need just a little more info.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 11:45 pm
p.s. A join to a Calendar table would be even more effective...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:58 pm
tickler_foryou (3/31/2008)
I have a Order_date column where order dates are captured in SQL server 2005 DB, I need to find the order dates that falls on Week Days only...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:56 pm
You'd be amazed what it can do... as you've seen, it'll do splits. It'll also fill in missing dates, generate multiple rows for each row according to a "QTY",...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:33 pm
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
Viewing 15 posts - 51,391 through 51,405 (of 59,098 total)