Discuss the difference between the ER model and Relational Model?

E-R Model and Relational Model both are the types of Data Model. Data Model describes a way to design database at physical, logical and view level. The main difference between E-R Model and Relational Model is that E-R Model is entityspecific, and Relational Model is table specific. Let us discuss some differences between E-R Model and Relation model with the help of comparison chart shown below.

Comments

Define the following terms: Entity, Attribute, Attribute Value, Relationship Instance, Composite Attribute, Multi-valued Attribute, Derived Attribute, Complex Attribute, Key Attribute, Value set(Domain), Recursive Relationships?

Entity – An entity can be a real-world object, either animate or inanimate, that can be easily identifiable. For example, in a school database, students, teachers, classes, and courses offered can be considered as entities. All these entities have some attributes or properties that give them their identity. Attribute – In general, an attribute is a characteristic. In a database management system (DBMS), an attribute refers to a database component, such as a table. It also may refer to a database field. Attributes describe the instances in the row of a database. Attribute Value – Attribute value is the real data of a particular entity for each of its attributes. In other word, associated with each real world entities are certain attributes that describe that entity; value of these attributes for any entity is called attribute value. For example, attribute value of first_name of attribute of student_name can be Gyanendra. Relationship Instance – Each relationship instance ri...

Define Primary Key, Candidate Key and Super Key?

Super Key Super Key is defined as a set of attributes within a table that uniquely identifies each record within a table. Super Key is a super-set of Candidate key. Example - Suppose we have a table that holds all the managers in a company, and that table is called Managers. The table has columns called ManagerID, Name, Title, and DepartmentID. Every manager has his/her own ManagerID, so that value is always unique in each and every row. This means that if we combine the ManagerID column value for any given row with any other column value, then we will have a unique set of values. So, for the combinations of (ManagerID, Name), (ManagerID, TItle), (ManagerID, DepartmentID), (ManagerID, Name, DepartmentID), etc – there will be no two rows in the table that share the exact same combination of values, because the ManagerID will always be unique and different for each row. This means that pairing the Manager ID with any other column(s) will ensure that the ...

TechSavvy

Search This Blog