MOD 1

1. List out any three database users and their functionalities.(3)

1. Database Administrator (DBA)
 They manage the entire database, ensuring everything runs smoothly.
 Responsible for securing the data and granting access to different
users.
2. Application Programmer / Developer
 They write programs to interact with the database, using code to add,
update, or delete data.
 They make sure that the data is stored and accessed correctly in the
database.
3. End User
 These are the people who use the database through applications
without knowing the technical details.
 They enter data or fetch information using simple interfaces like web
pages or apps.
2. Distinguish between schema and instance.(3)
Feature Database Schema Database Instance
Definition The structure or blueprint of the database The actual content or data stored in the
that defines how data is organized and database at a specific point in time.
related.

When it is Designed when the database is initially set Changes frequently as data is inserted,
created up; it does not change often. updated, or deleted in the database.

Contains Does not contain any data itself; it's just a Contains data at any given moment; it's a
Data design or skeleton. snapshot of the current state of the
database.

Purpose Defines the overall design and structure of Represents the current state of the
the database. database with data at that moment.

Example Tables, columns, and relationships between Data like customer names, orders, and
tables. products.
3. List any SIX major advantages of using a DBMS(3)(6 points)
1. Controlling Redundancy
Prevents duplication of data, saving storage space and ensuring
consistency.
Example: Stores information like a student’s name in only one place.
2. Controlling Inconsistency
Ensures data remains accurate and free from conflicting information.
Reducing redundancy also reduces inconsistency.
3. Data Integrity and Security
Maintains data accuracy and enforces access controls for security.
Example: Ensures only authorized users can view or modify salary data.
4. Facilitating Data Sharing
Allows multiple users to access and use the same data for different
purposes.
Example: Various departments can share customer data for reports and
analysis.
5. Concurrent Access and Crash Recovery
Manages multiple users accessing data simultaneously without errors.
Protects data from being lost during system crashes.
6. Providing Backup and Recovery
Creates backups and restores data in case of system failures.
Example: Restores the database if a system crash occurs during a
transaction.

4. What is the concept of a weak entity used in data modelling? Define the
terms entity type, Identifying relationship type.
 An entity set may not have sufficient attribute to form a primary key is
termed a weak entity set.
• An entity set that has a primary key is termed as strong entity set.
• For a weak entity set to be meaningful, it must be associated with another
entity set, called the identifying or owner entity set.
• A weak entity set does not have a primary key.
  Weak entities are represented with double rectangular box in the ER
diagram and the identifying relationships are represented with double
diamond.
 In the above ER Diagram, ‘Payment’ is the weak entity. ‘Loan Payment’ is
the identifying relationship and ‘PaymentNumber’ is the partial key.

5. List any three characteristics of database system(3)

 Provides scurity and removes redundancy
 Self-describing nature of a database system
 Insulation between programs and data abstraction
 Support of multiple views of the data
 Sharing of data and multiuser transaction processing DBMS allows entities
and relations among them to form tables.
 It follows the ACID concept Atomicity, Consistency, Isolation, ad.
Durability) DBMS supports multi-user environment that allows users to
access and manipulate data in parallel.
6. Draw neat labelled diagram of three schema architecture and briefly
describe 3 each level(3 or 7)

The Three-Schema Architecture is a framework used in database systems to

separate the user's view of data from the physical storage of data. It defines
three levels of abstraction: the conceptual level, the physical level, and the
external level, each serving different purposes in how data is managed,
accessed, and presented to users.
 Conceptual Level: This level defines what data is stored in the database and
how it is organized. It focuses on the logical structure of the database, such
as tables, relationships, and constraints, and hides the physical storage
details. Database administrators and programmers work at this level to
design the database.
 Physical Level: The physical level describes how the data is actually stored
on storage devices like hard disks or tapes. It includes the storage structures
and access methods (e.g., B+ trees, hash tables) for efficient data retrieval.
Users do not interact with this level.
 External Level: The external level provides customized views of the
database for different users or user groups. It is the closest to the user,
offering data in a way that suits the user’s needs without revealing how the
data is stored or organized internally. Different users may have different
views based on their requirements.
7. What are the major difference between structured, unstructured and
semi 3 structured data.(3)

8. Explain the seven drawbacks of file processing system, compared to

database 7 approach.
Aspect File Systems DBMS
Data Storage Data is kept in different Data is stored in a
files. centralized database.
Data Redundancy Data may be duplicated Redundancy is
in multiple files. controlled by storing
data in one place.
Data Consistency Data can become wrong Data stays correct and
or outdated in different up-to-date in one place.
files.
 Data Sharing It's hard to share data Data can be easily
between programs. shared between
different users.
Standardization Data formats are not Data formats are the
the same in every file. same, making it easy to
work with.
Data Security Security is limited to Strong security features
the file itself. control who can see the
data.
Data Integrity Data can get messed up Data stays correct
if not handled carefully. through rules that
prevent mistakes

9. Represent a "Library Management Software" using an ER

diagram.(7)

10. Represent an "Online Shopping Portal" using an ER diagram.(7)

11.
12. Difference between Physical data independence and logical data
independence.(6)
13.

i. List the strong (non-weak) entity types in the ER diagram.

Strong entity types are entities that can exist independently and have a
primary key. From the description:
Home
Owner
Agent
Office
Buyer
ii. Is there a weak entity type? If so, give its name, partial key, and
identifying relationship.
Yes, there is a weak entity type.
Weak Entity Name: Home
Partial Key: Home Identifier
Identifying Relationship: "Owned by" or the relationship with the
Owner, as the home cannot exist without an owner.

iii. What constraints do the partial key and the identifying relationship of
the weak entity type specify in this diagram?
The constraints are:
Partial Key Constraint: Ensures the uniqueness of a home when
combined with the owner's identifier.
Identifying Relationship Constraint: Each home must be associated with
exactly one owner to establish its identity.

iv. List the names of all relationship types and specify the (min, max)
constraint on each participation of an entity type in a relationship type.
Relationships and Constraints:
Owns (Owner ↔ Home):
Owner (1, n)
Home (1, 1)
Lists (Agent ↔ Home):
Agent (1, n)
Home (0, 1)
Works At (Agent ↔ Office):
Agent (1, 1)
Office (1, n)
Buys (Buyer ↔ Home):
Buyer (1, 1)
Home (0, n)
Associates (Buyer ↔ Agent):
Buyer (1, 1)
Agent (1, n)

v. Suppose that every customer must have at least one account but is
restricted to at most two loans at a time, and that a bank branch cannot
have more than 1,000 loans. How does this show up on the (min, max)
constraints?
Customer ↔ Account: (1, n) for the customer, indicating at least one
account.
Customer ↔ Loan: (0, 2) for the customer, restricting the maximum
number of loans to two.
Branch ↔ Loan: (0, 1,000) for the branch, restricting loans to a
maximum of 1,000 per branch.