best way to set up a linked database to search addresses?

[nimarii]

Hello,

I have a database (db1), a big part of which involves locations(street, city, state, zip, customername, etc). I also have a huge excel spreadsheet (20,000 records and counting) of addresses for different customers.

What I need to do is get this excel spreadsheet into a database (db2), and then link this to db1. For example, in db1, I want to set up a tool that allows the user to enter in an address, click a button that queries db2, and returns the customer name, if a match is found.

I'm unsure of how to set up db2 though. Should I split the data by state, and have 50 tables, or just put all the data into one big table?

any other suggestions are more than welcome!

 

[SQLSister]

What database are you using? I would, in general, simply import the Excel sheet as a new table in the existing database and query like any other table.

Questions about posting. See faq183-874

 

[nimarii]

I'm using an Access database for both of them. Eventually, I will be moving to SQLserver, but not for some time. My main concern about importing the spreadsheet into one giant table, is the length of time it will take to query 20,000+ records.....

 

[SQLSister]

20,000+ records is nothing even for Access. Query time should be fairly low. For SQL Server it would be considered a small table.

Questions about posting. See faq183-874

 

[bitmite]

if you put it in a seperate db that will slow down the query time a little go I would keep it together.

Brought to you By Nedaineum
The Portal to Geek-tum

 

[1oldfoxman]

I agree with what's been said above, and specifically would not recommend splitting any database into 50 tables by state. Think you'd be hard pressed to invent a situation where that would make sense and it would likely lead you down a road where insanity is the only destination.

 

[nimarii]

Thanks for the replies! 1oldfoxman & bitmite, I will keep it all in one db, and won't split up the tables either.
wish me luck!

nimarii