define too much redundancy using -'sql,relational-database,normalization,redundancy'

define too much redundancy  using -'sql,relational-database,normalization,redundancy'

I'm doing an online course and it gives the following relvar example and then says:

¬†¬†Hmm. Although answer and answercode are different in each tuple‚ÄĒmaking
¬†¬†each tuple technically unique‚ÄĒthe values for attributes id,
  questionID, and answertype are exactly the same. Normalization is in orderd.

Question is, what is considered too much redundancy? Where is the line drawn before we start going through normalization steps?

asked Sep 7, 2015 by rajesh
0 votes

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:
To avoid this verification in future, please log in or register.