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.
For example, if i store a redundant column in one table, i can avoid joining 5 tables in runtime SQL queries. In cases such as this, is it justifiable to store redundant data? My understanding is that it violates the rules of normalization but I’m not a db expert.
Thanks for any advice.
In my experience, denormalizing for performance is not in itself an evil, but you need to check first that you cannot optimize the queries that you run against your initial 3NF design to give you reasonable timing.
Here is a link to a nice article suggesting that reduction in the number of joins is a common (and good) reason to denormalize.