Viewing 15 posts - 43,846 through 43,860 (of 59,101 total)
The artical that Paul White pointed us to about the peformance difference between SELECT and SET is pretty close to spot on percentage wise. I'm just not one to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2009 at 7:30 pm
Barkingdog (5/9/2009)
1. Temp 550GB was not enough. t-sql job ran into 550GB limit and failed.
2. Found statement causing the issue. The essence is shown below:
insert into
..
select distinct ....
....
from
tableA join...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2009 at 6:22 pm
Wow... that's a heck of a table. I am so not jealous of either that or the rigors they seem to be putting you through.
Thanks for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2009 at 9:55 am
Manie Verster (5/9/2009)
You only put A-Z and not also a-z. How does that work?
Peter gave a pretty good description as to why. To simplify, the default for SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2009 at 9:23 am
Florian Reischl (5/9/2009)
Jeff Moden (5/9/2009)
BTW - It is good to see growing acceptance of the idea that ANSI standards are kinda 'blah'. I couldn't agree more π
Man, I agree...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2009 at 8:52 am
John Esraelo (5/9/2009)
have not we have had kicked this dead horse plenty..I think we did..
:))
The bones of these types of dead animals are interesting... its especially interesting to see how...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2009 at 7:57 am
Paul White (5/9/2009)
Jeff Moden (5/8/2009)
Paul White (5/8/2009)
When assigning multiple variables from constants, SELECT is significantly quicker than separate SET statements.
Heh... I agree, but where's the code to prove that? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 9, 2009 at 7:53 am
Paul White (5/8/2009)
John,When assigning multiple variables from constants, SELECT is significantly quicker than separate SET statements.
Just adding that for completeness.
Paul
Heh... I agree, but where's the code to prove that? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2009 at 8:00 pm
RBarryYoung (5/8/2009)
*sigh* I'm so misunderstood. π
Heh... it's the helmet, Barry... can't see your eyes. π
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2009 at 7:58 pm
John Esraelo (5/8/2009)
1> code portability, because of the systems and software shelf-life and change in technology
I don't believe in the myth of code portability. Consider first that even the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2009 at 7:56 pm
Yep... the TOP 100 PERCENT thing works just fine although a whole lot of people will tell you
that order shouldn't matter in most processing. Except for things like...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2009 at 7:37 pm
Yah... you're right... 1 in a row. π
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2009 at 4:52 pm
PhilM99 (5/8/2009)
Here are the data as attached files...
Those files look pretty good. Instead of me trying to weed through this whole post, care to "nut shell" the problem you're...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2009 at 3:24 pm
Just another test... (nothing has changed... all faults still present especially when copy from the forum to QA or SSMS).
drop table tally
GO
--===== Create and populate the Tally table on the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2009 at 3:08 pm
SELECT TOP 100 PERCENT * FROM --was 3000
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2009 at 3:03 pm
Viewing 15 posts - 43,846 through 43,860 (of 59,101 total)