Will my database choke up if...

[$var]

Can anyone tell me some negatives about designing a relational database in MySQL that has the potential to grow to 100,000's of entries.

I work for an events company, and each event has speakers, and sponsors, and they all belong to different industries and business units... which means, a lot of cross checking.

for example, i am going to set it up like this, all these ID's relate to the 1 event:
Event_ID
Event_UnitID
Event_IndID
Event_SubIndID
Event_VenID
Event_CityID

Spk_EvntID ()

Sponsor_EvntID ()

Is this going to be too much in the future? Should I be worried that by splitting up all the information into different table, and using
SELECT * FROM ### WHERE ID=$ID;

I'm sort of novice as far as DB building goes... and I don't want it to explode on itself in 2 years after it has to look through 10000 records to find the Event_ID the Spk_EventID corrosponds to?

Or is that just how it's supposed to work, and that's what databases are built to do? Is SQL sturdy enough to handle it?

[russell]

no worries -- that's the right way to do it. u wont want to select * though, you should specify filed names in your select statement. make sure to index apporpriate fields for best performance once tables start growing

[$var]

thanks for the reassurance russell.

i'm not sure what you mean though by specify filed names in the select statement

[russell]

instead of select *

something like this
SELECT name, address, city, state, zip