Viewing 15 posts - 256 through 270 (of 309 total)
Paul White NZ (4/14/2010)
April 14, 2010 at 10:58 am
Paul White NZ (4/14/2010)
I said the question had been well answered - I'm just exploring an alternative for large inputs....
April 14, 2010 at 8:13 am
Interesting concept.
Unfortunately If I am not missing something, it will not really work correctly.
Consider the following consecutive rows in the IpToCountryMap table:
from_ip to_ip ...
April 14, 2010 at 5:13 am
Paul, I find your knowledge of the internal workings of SQL Server very impressive.
How do you know all this internal stuff ?
April 14, 2010 at 1:22 am
What I mean is try rewriting the from clause of the query like this:
from #FL as a inner HASH join Obbeaver.State_FL.dbo.HomeLook_USA as b on a.Clmn10 = b.Clmn10
left join Obbeaver.State_FL.dbo.VwOffLook_USA...
April 13, 2010 at 7:56 am
Tara-1044200 (4/13/2010)
April 13, 2010 at 7:39 am
Tara-1044200 (4/13/2010)
April 13, 2010 at 7:12 am
You are reading 32 million rows from HomeLook_USA with a remote query. The optimizer estimates this remote query to return only 570 rows.
This extreme difference in estimated rows and actual...
April 13, 2010 at 6:16 am
I dont know why your numbers are so strange. Perhaps your system was heavily loaded ?
I ran the same test on my unloaded 2-CPU laptop and I got the following...
April 13, 2010 at 5:22 am
Jeff Moden (4/12/2010)
On the subject of a non-clustered index in a similar order at work... it caused very frequent timouts but, admittedly, that was on a table with a fair...
April 13, 2010 at 1:01 am
Jeff Moden (4/12/2010)
Stefan_G (4/12/2010)
1) Add a nonclustered index on CountryCode, IpNumber on [my].[ipAddresses]
It'll make for a fine nonclustered index. Using it as a clustered index can cause a lot...
April 12, 2010 at 5:08 pm
Jeff Moden (4/12/2010)
Stefan_G (4/12/2010)
1) Add a nonclustered index on CountryCode, IpNumber on [my].[ipAddresses]
Ohhhh... be careful now. Unless that index is applied after all data is present and no new...
April 12, 2010 at 3:47 pm
It sure sounds like you could benefit from partitioning.
It sounds like you have a very large table with data that covers a long time period and the table only gets...
April 12, 2010 at 11:34 am
I actually found such a formula myself by modifying code found at
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=66471
Here is the code:
DECLARE @IntDate INT
SELECT @IntDate = 20090117
dateadd(month,((@IntDate/10000-1900)*12)+((@IntDate/100)%100)-1,(@IntDate%100)-1)
But, the performance of this expression is actually...
April 12, 2010 at 10:55 am
I would say option 1) There is no performance difference between the index used for the primary key and any other non-clustered index.
Instead of placing different objects in different filegroups,...
April 12, 2010 at 10:38 am
Viewing 15 posts - 256 through 270 (of 309 total)