Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Creating Tables

Status
Not open for further replies.

jjones100

Technical User
Nov 12, 2004
23
US
I am wondering which design would be better for my new tables. In the past I have just had one table with ALOT of fields. I am creating a new db and am wondering if I should split the info into multiple tables. I have a ckt id field that all other fields relate to, such as customer address, ckt type, service type etc. I screen scrape information from a mainframe to populate my fields. The join would be the ckt id(obviously this would be a dup in each table), but i am wondering what the benefit of multiple tables would be. Less corruption, better performance? Thanks
 
I have a ckt id field that all other fields relate to
Are the other fields all populated in every row ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Not ever record has every field populated. It depends on the ckt type. I am just debating having to open several tables for the screen scraping and having all of those joins.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top