Viewing 15 posts - 33,496 through 33,510 (of 59,099 total)
David Lester (6/22/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2011 at 9:26 am
matt6749 (6/25/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2011 at 9:13 am
Ken McKelvey (6/24/2011)
I am trying to write an inline splitter function based on Jeff Moden’s recent article,...
It seems that things have gotten a bit complex on this problem and I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2011 at 8:46 am
I know the answer is "because they're twits", but why are twits always compelled to finish with a nasty remark?
http://www.sqlservercentral.com/Forums/FindPost1131551.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2011 at 12:48 am
ark.trofman (6/24/2011)
So, please, could you learn English first, and then look from your unreachable heights down at the people who try to publish here ?
You were doing fine right up...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2011 at 12:19 am
Oh yeah... I almost forgot. Part of the problem with the original code and the reason why it could only do a Clustered Index Scan was because of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 10:30 pm
p.s. That code uses 2 Index Seeks. One for the first single row lookup and the other to find the 1,333 ZipCodes in the Latitude Optimization for a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 9:54 pm
Ok... here's the way I'd do this job so that I can get the best speed possible out of it.
First, you have to dump that scalar function for Distance and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 9:50 pm
Just so you know, I'm working on this and I've solved the problem of the Clustered Index Scan. I've just got some more to do on it.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 6:56 pm
opc.three (6/24/2011)
Be careful with table variables. They always optimize with an assumed rowcount of 1 so can produce very bad execution plans...even with small actual rowcounts.
A statement level OPTION(RECOMPILE) will...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 3:17 pm
Craig Farrell (6/24/2011)
Jeff Moden (6/24/2011)
Craig Farrell (6/23/2011)
This conversation resparked a curiousity on my part.
When I run that code as a single unit, it keeps returning the following error...
There is already...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 3:14 pm
I wasn't going to post until I got home from work to give some demo's (I don't have time while at work) but one of the things to consider (that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 10:28 am
THE-FHA (6/24/2011)
SQL 2008 come with query execution plan and estimation. try testing this queries and see the estimated results.
Nah... the execution plan frequently lies for things having to do with...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 10:25 am
opc.three (6/24/2011)
Jeff Moden (6/24/2011)
Craig Farrell (6/23/2011)
This conversation resparked a curiousity on my part.
When I run that code as a single unit, it keeps returning the following error...
There is already an...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 10:23 am
THE-FHA (6/24/2011)
Ever thought of the Query Analyzer?the first option is best.
What on Earth are you talking about? First Query Analyzer is for 2000 and second, I meant running running...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2011 at 10:22 am
Viewing 15 posts - 33,496 through 33,510 (of 59,099 total)