I'm confused, a LEFT JOIN returns all the rows from the table, which I don't want..

Oh my gosh Jeff, after being puzzled about why the join would affect the execution time so much (Providers table only has 2500 records, Occupations table only 10 records)

.. I...

Hi Jeff:

- I have the indexes you recommended on my ZipCode table

I implemented your code and it reduced the query times:

OLD TIMES:

~850ms for '10023'

~2600ms for 'V6H 1E2'

NEW TIMES:

~300ms for '48326'

~1100ms...

Jeff - Thank you SO much for your help. Your brain power is really impressive. Now I'm reminded why I can't get programming jobs very easily! lol....

Jeff Moden (6/24/2011)

---

@matt6749,

Please post the code for fnDistance and then I'll tell you why there's such a time difference. I might also be able to tell you how to...

Jayanth_Kurup (6/24/2011)

---

Form past experience NO , the data volume will result in slower query performance , but in no way are the proportional , i.e double the data <> 1/2...

Yes, I will look at the query plan more. However, my general question remains - a radius search with 44k zip records is going to be slower that a...

Sriram.RM (6/24/2011)

---

Ideally Addition of 750000 records shouldn cause much problems.... Did you check the execution plan?

If you want any of us to analyze further into the issue i suggest...

Yes, rebuilt indexes.. My guess is that the increased query time makes...

RE: Gail's article, very good, but I don't think it's necessary for this general question.

tx for the info, but i didn't understand what you are saying..

It is SQL 2008.

yes, but HOW to update - re-run the same params as the SELECT query only as an UPDATE query? that seems arduous, and database and processor intensive.

varunfilim (7/19/2010)

---

Hi,

You can...

Thanks Todd - I have only used the "Max Latitude" limiter cause it was pretty simple. I haven't implemented the other part of the "square" - the max longitude...

Thanks Dave - My zip code table has about 40,000 records. I now understand and implemented a "latitude limiter"

DECLARE @start_lat float

DECLARE @MaxNorthLat float

DECLARE @MaxSouthLat float

SELECT @start_lat = (SELECT...