A Normal Form for Preventing Redundancy in Relational databases | Search for a title, author or keyword | ||||||||
A Normal Form for Preventing Redundancy in Relational databases PDF document by Hugh Darwen, C. J. Date, Ronald Fagin. 2012. Database design can be characterized as a matter of deciding what the database schema should be - that is, of deciding what attributes (intuitively, column names) should be in each individual relation schema, and what the constraints should be on the data. It has always been a goal of database design to make the database schema as redundancy-free as possible, and ever since the publication of Codd's first papers on the subject, the discipline of further normalization (normalization for short) has been used to help achieve that goal. In this paper, we define what it means for a tuple in a relation to be redundancy-free, or "essential", and we define a normal form where every tuple is essential.
|
|||||||||
A Normal Form for Preventing Redundancy in Relational databases | Disclaimer: this link points to content provided by other sites. |