We design this database to track our customer database but I feel it is little complicated design I feel it can be more simple can someone give some advice for design?


Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If simplicity is the key point here, I’d suggest you collapse your customer-related address type information into a single table like so :
The contact_type field can then be tagged as
Home Phone,email,primary_email,work_phone,primary contactdepending on your needs. You can then have all such related contact information in a single table. Streamlines your schema and you need only a single join to make sense of the info.