Question on database layout

[danedwards11]

I am somewhat inexperienced at creating databases. I am a long-time programmer, but fairly new to database design.

I am creating a new project which stores database records of incoming phone calls. Each phone call gets a new record. Also, each phone call has various properties that I need to use to access the call, such as:
Phone # the caller dialed dialed
Phone # of caller (caller id or ANI)
Extension that answered the call
Agent that handled the call
-- and others --

The obvious solution seems to me to have a single table with all the properties as fields, then index the fields I need to search on. Is this in fact the best approach or can I get some advantages by creating multiple tables which contain the various properties that link back to a unique ID for the call record.

Thanks for any hints, pointers, etc. you might provide.

[newdles]

One major warning I can give you that will save alot of headaches.... Don't use the int data type. You'll hate yourself if you do.

Reason why is let's say that you have a phone call come in. The data would be:

555-5555
444-4444
01
John Doe

If 01 is intered as an int, it will reas as 1 and not 01 as entries starting with 0 are considered letters no matter what.