Name : Om Dhinoja Email: dhinoja.o@northeastern.

edu
NEU ID: 002832284 Assignment: 4

Q1.
Ans 1.] The purpose of logical database design is to transform the conceptual data model into a logical data
model that is consistent and compatible with a specific type of database technology. Logical database design
involves translating an organization’s requirements for data as captured in the conceptual design into a
structured, stable format that can be implemented by a database management system. It ensures that the
resulting database meets user needs for data sharing, flexibility, and ease of access, while also being correctly
expressed in technical terms to support sound database processing. This step is crucial for creating stable, well-
structured database environments.

Q2.
Ans 2.]
1. Each relation (or table) in a database has a unique name.
2. An entry at the intersection of each row and column is atomic (or single valued). There can be only one
value associated with each attribute on a specific row of a table; no multivalued attributes are allowed in
a relation.
3. Each row is unique; no two rows in a relation can be identical.
4. Each attribute (or column) within a table has a unique name.
5. The sequence of columns (left to right) is insignificant. The order of the columns in a relation can be
changed without changing the meaning or use of the relation.
Q3.

Ans 3] A key property of candidate keys that makes them suitable for unique identification is that they must
contain only unique values and cannot include null values. This ensures that every row in the table is distinct, as
the candidate key uniquely identifies each record. Because a candidate key must be both unique and non-null, it
guarantees that no two rows will have the same key value, making it an effective mechanism for uniquely
identifying records in a relational database

Q4.

Ans 4] Referential integrity constraints play a crucial role in maintaining data consistency within the relational
model by ensuring valid relationships between tables. These constraints require that a foreign key in one table
either matches a valid primary key in another table or is null. This prevents invalid data from being entered or
breaking links between related records. For example, it ensures that a record in one table cannot reference a
non-existent record in another table, and it restricts the deletion of records that are being referenced by other
tables. By enforcing these rules, referential integrity helps maintain the overall integrity and consistency of the
database.

Q5.
1
Name : Om Dhinoja Email: [email protected]
NEU ID: 002832284 Assignment: 4
Ans 5] In logical database design, multi-valued attributes are those that can hold more than one value for a
single entity, which is not allowed in a relational database as it requires each attribute to contain a single, atomic
value. To address this, multi-valued attributes are handled by creating a separate table to store the multiple
values. For example, if an employee can have multiple skills, instead of storing all the skills in one row, a
separate Employee_Skills table is created where each row contains one EmployeeID and one Skill. This ensures
that each entry in the database remains atomic and follows the principles of relational database design.

Q6.
Ans 6] Data integrity constraints are rules enforced on a database to ensure the accuracy, consistency, and
reliability of the data stored within it. These constraints include domain constraints, which specify that the
values in a column must belong to a defined domain; entity integrity, which ensures that the primary key for
each table is unique and cannot be null; and referential integrity, which ensures that relationships between tables
remain consistent by requiring that foreign keys correspond to valid primary keys in related tables. These
constraints are essential because they prevent errors, inconsistencies, and unauthorized modifications, ensuring
the database reflects accurate and reliable information. By enforcing data integrity, these constraints maintain
the quality of the data and the proper functioning of the database as a trusted source of information.

Q7.
Ans] The primary key and unique key constraints both enforce uniqueness in a relational database, but they
have key differences. A primary key uniquely identifies each row in a table and cannot contain null values; there
can only be one primary key per table, serving as the main identifier for records. In contrast, a unique key also
ensures uniqueness for a column or combination of columns but allows for multiple unique keys within the
same table and can accept null values (though only one null is permitted per unique key column). Thus, while
both constraints maintain data integrity, the primary key acts as the principal identifier, whereas unique keys
provide additional uniqueness constraints across different columns.

Q8.
Ans] A foreign key constraint is a rule in a relational database that establishes a link between two tables by
ensuring that the value in a foreign key column matches a valid primary key in the referenced table or is null.
This constraint is crucial for maintaining referential integrity, which ensures that relationships between tables
remain consistent. By enforcing foreign key constraints, the database prevents the insertion of records that
reference non-existent entries in the related table, thus avoiding orphaned records. Additionally, it regulates
actions such as updates and deletions; for instance, if a record in the primary key table is deleted, the database
can be configured to either restrict the deletion, cascade the deletion to related records, or set the foreign key to
null, thereby maintaining the integrity and consistency of the data across the database.