The Eduladder is a community of students, teachers, and programmers just interested to make you pass any exams. So we solve previous year question papers for you.
See Our team
Wondering how we keep quality?
Got unsolved questions?

Ask Questions

Hey, We have just launched eduladder videos.Looking for creators and contributors Read Guideline
Database-Management-Systems---10CS54-VTU-notes-->View question

Explain informal design guidelines for relation schemas. Database Management Systems - 10CS54 VTU notes (Dec /Jan 12/Jan 2016)

Explain in brief? 


Taged users:

Be first to like this question

Be first to dislike this question

Talk about thisDelete|Like|Dislike|


The four informal measures of quality for relation schema • Semantics of the attributes • Reducing the redundant values in tuples • Reducing the null values in tuples • Disallowing the possibility of generating spurious tuples Semantics of relations attributes Specifies how to interpret the attributes values stored in a tuple of the relation. In other words, how the attribute value in a tuple relate to one another. 

Guideline 1: Design a relation schema so that it is easy to explain its meaning. Do not combine attributes from multiple entity types and relationship types into a single relation. Reducing redundant values in tuples. Save storage space and avoid update anomalies. 


Be first to like this answer

Be first to dislike this answer
Talk about this|Once you have earned teacher badge you can edit this questionDelete|Like|Dislike|

Can you help us to add better answer here? Please see this

Not the answer you're looking for? Browse other questions from this Question paper or ask your own question.

Join eduladder!