Viewing 15 posts - 43,036 through 43,050 (of 59,102 total)
Also, here's what the new zipless sqlplan does in IE...
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2009 at 6:11 am
Mel Harbour (7/15/2009)
Ok, I've run a modified version of Jeff's suggestion:
Something sure is wrong... look at the difference between the CPU and the duration compared to my box.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2009 at 6:02 am
Okidoki... thought I'd throw my hat into the ring on this, as well. I didn't try G-Squared's code yet, but here's mine.
First, the test harness. It create a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 15, 2009 at 1:01 am
I think I found out how many... would it be right around 106,916?
The only thing I need to know now is how many users are in the Users table? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 11:01 pm
Mel Harbour (7/13/2009)
The UserPoints table currently has about 185,000 rows. Execution plans are attached.
Mel... I'm trying to setup the proverbial parallel universe for testing and need just a wee bit...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 7:36 pm
What I meant by the BETWEEN was, if you have a zero-based table and need a unit-based solution, then the WHERE clause would need to include WHERE N BETWEEN 1...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 7:08 pm
Here's the trace from my home machine...
And, here's the code I'm running... All I did was take your code, remove your comments, add mine, make each query dump to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 5:46 pm
Something else is going on as well. Look at the difference in durations on your machine compared to mine. The machine I have at work is just a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 4:24 pm
GilaMonster (7/14/2009)
But on a single statement insert the rows will be sorted before they're inserted if they're inserted into a table with a cluster, so there won't be page splits.
Ach......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 1:46 pm
GilaMonster (7/14/2009)
Jeff Moden (7/14/2009)
Jack Corbett (7/14/2009)
Was Jeff referring to the Order By in the ROW_NUMBER() function?Yes.
Ok, misunderstood you earlier. Are you suggesting adding a second temp table, one to store...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 12:59 pm
Jack Corbett (7/14/2009)
Was Jeff referring to the Order By in the ROW_NUMBER() function?
Yes.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 10:54 am
GilaMonster (7/14/2009)
Christopher Stobbs (7/14/2009)
but creating the clustered Index on #TopScores after the actual insert?Would this help at all?
If the cluster goes on after the insert then first SQL has to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 10:53 am
Mel,
I haven't had the time to look at all the fine suggestions folks may have given, but if I look at your original query, I see the potential for a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 5:48 am
You bet. Thank you for the feedback.
As a bit of a sidebar, NULLs are some of the oddest things and can also be a very, very powerful tool depending...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 5:30 am
cb (7/13/2009)
Whilst everything you say is true, the environment I have to deal with is:
Software vendor creates a product based on SQL, and sells it to client.
Client wants some...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2009 at 5:19 am
Viewing 15 posts - 43,036 through 43,050 (of 59,102 total)