Re: Suggestions for breaking large table into smaller?

2002-10-18 Thread Michael T. Babcock
Brent Baisley wrote: about the same amount of time, then you don't have a proper index. The query above needs to read the entire table to compile the stats, your query should just need to read the records that are NJ if it really is using the index correctly. The results would also be inter

Re: Suggestions for breaking large table into smaller?

2002-10-18 Thread Brent Baisley
That is not normalizing your data. Normalization would be to create a States table that would list all states (perhaps having abbreviation, full name, country, etc) and then you would only store a code linking to the states table. Although this is one of those special cases where full normaliza

RE: Suggestions for breaking large table into smaller?

2002-10-18 Thread Arthur Fuller
If your contacts are all North American, and this is a typical query, you may well profit significantly from normalizing the address data. To do so, create a Cities table and a States table (perhaps call it Regions if you need to account for CDN provinces). The Cities table would look like: CityID