Reputation: 1
I have a database like
Customer_ID Customer_Lastname Customer_Name Customer_Address
Should I store all these infos in just one table or should I make tables like
Customer_ID Customer_Lastname Customer_Name
and
Customer_ID Customer Address ?
regards
Let me detail it more.. I want the app get results as fast as possible. Having 100 tables wont slowdown the app ? Or having only the neccessary info in a table makes it faster ?
I have around 30.000 ID and each has almost 30 different data such as add, name, products they use and their CR managers etc.
Regards
Upvotes: 0
Views: 85
Reputation: 425198
Use just one table.
There is no motivation to split it based on your question and my experience.
There is motivation to leave it in one... simpler queries and less I/O to retrieve data.
Later comments reveal that you want customers to have multiple addresses. In that case, a second table would be warranted:
Table address:
address_id, customer_id (FK), address_name, <address fields as you need>
address_name
would be the nickname, eg "Home", "Office", "Aunt Jenny" or whatever as named by the user.
Upvotes: 1
Reputation: 5184
I say one table for now but don't use just Customer_Address. Break address up into separate fields:
Address1
Address2
City
State
ZipCode
Upvotes: 0