DBMS UNIT 1

Q1. Explain the concept of two-tier architecture.

Introduction
There are several types of DBMS Architecture that we use according to the
usage requirements. Types of DBMS Architecture are discussed here.
One-Tier Architecture
Two-Tier Architecture
Three-Tier Architecture
Two-Tier Architecture

The 2-tier architecture is similar to a basic client-server model. The application

at the client end directly communicates with the database on the server side.
APIs like ODBC and JDBC are used for this interaction. The server side is
responsible for providing query processing and transaction management
functionalities. On the client side, the user interfaces and application programs
are run. The application on the client side establishes a connection with the
server side to communicate with the DBMS.

An advantage of this type is that maintenance and understanding are easier,

and compatible with existing systems. However, this model gives poor
performance when there are a large number of users.

DBMS 2-Tier Architecture

Advantages of 2-Tier Architecture
 Easy to Access: 2-Tier Architecture makes easy access to the
database, which makes fast retrieval.
 Scalable: We can scale the database easily, by adding clients or
upgrading hardware.
 Low Cost: 2-Tier Architecture is cheaper than 3-Tier Architecture
and Multi-Tier Architecture.
 Easy Deployment: 2-Tier Architecture is easier to deploy than 3-Tier
Architecture.
 Simple: 2-Tier Architecture is easily understandable as well as
simple because of only two components.

Q2. What are the main problems with traditional file processing
systems? (miaaaaaaawww)
Introduction

Traditional file processing systems create numerous challenges for

organizations due to their fragmented and uncoordinated nature. Each
department—whether it's accounting, finance, manufacturing, human
resources, or sales—develops its own applications and data files
independently, leading to several key problems.

First, there's the issue of **data redundancy and inconsistency**. When

different departments store the same data separately, it results in duplication
and discrepancies. For example, an order's quantity might be updated in one
system but not in another, leading to confusion and errors. This not only
wastes storage space but also makes it hard to trust the data's accuracy.

Another major problem is **program-data dependence**. This means that

the data files are tightly linked to the programs that use them. So, if you
change the format of a data field, like expanding a ZIP code from five to nine
digits, you need to update every program that accesses that data. This can be
incredibly costly and time-consuming.

The traditional file system also **lacks flexibility**. While it can handle
routine reports, generating new or unexpected information often requires
significant programming effort. This makes it difficult to quickly retrieve the
data you need for sudden, ad hoc requests.

**Poor security** is another significant concern. Because there's no

centralized control, managing who has access to the data is tough. This can
lead to unauthorized access and changes, putting sensitive information at risk.

Finally, there's the **lack of data sharing and availability**. With data
scattered across different departments, it's challenging to get a complete
picture. Information doesn't flow smoothly between areas, making it hard to
combine data for analysis and decision-making. This fragmented approach
results in inefficiencies and hampers the organization's ability to act on
comprehensive insights.

Summary:
In essence, traditional file processing systems are fraught with inefficiencies
and obstacles that make effective data management, security, and
collaboration difficult. These issues can significantly hinder an organization's
agility and decision-making capabilities.

Q3. What is database Abstraction in database management system

Introduction
Data abstraction in a DBMS is about hiding the detailed, technical aspects of
how data is stored and managed. This makes it easier for users to access the
data they need without worrying about the complex stuff behind the scenes.
Purpose of Data Abstraction
- Hiding Unnecessary Details: Users only see the data they need.
- Simplifying User Interaction: Users can get the data they want without
understanding how it’s stored.
- Improving System Performance: The system runs better by handling
complexity internally.

Levels of Data Abstraction

1. Physical or Internal Level:
- What it is: The lowest level of data abstraction. It focuses on how data is
actually stored.
- Details: Includes complicated data structures, ways to access data, and
storage information.
- Managed by: Database Administrators (DBA).
- Storage: Data is stored on hard drives in data centers.
- User Interaction: Hidden from users because it’s too complex.

2. Logical or Conceptual Level:

- What it is: The middle level of data abstraction. It shows what data is
stored and how different data pieces are related.
- Details: Organizes data into tables and defines relationships.
- Managed by: Database Administrators (DBA).
 - User Interaction: Easier to understand than the physical level, but not
directly used by most users.

3. View or External Level:

- What it is: The highest level of data abstraction. It provides different views
of the database for users.
- Details: Different views are created to meet the needs of different users.
- User Interaction: Directly accessed by users, showing only the data they
need.

Advantages of Data Abstraction in DBMS

- Ease of Access: Users can get the data they need easily.
- Security: Keeps data safe by showing only necessary information.
- Efficiency: Makes the system work better by handling complexity internally.

By organizing data into these levels, a DBMS ensures users can interact with
the data simply and securely, while the system remains efficient and strong.

Q4. What is three-tier architecture and how does it work?

Introduction
There are several types of DBMS Architecture that we use according to the
usage requirements. Types of DBMS Architecture are discussed here.
One-Tier Architecture
Two-Tier Architecture
Three-Tier Architecture
Three-Tier Architecture:
In 3-Tier Architecture, there is another layer between the client and the server.
The client does not directly communicate with the server. Instead, it interacts
with an application server which further communicates with the database
system and then the query processing and transaction management takes
place. This intermediate layer acts as a medium for the exchange of partially
processed data between the server and the client. This type of architecture is
used in the case of large web applications.

Advantages of 3-Tier Architecture:

1.Enhanced scalability: Scalability is enhanced due to the distributed
deployment of application servers. Now, individual connections need not be
made between the client and server.
2.Data Integrity: 3-Tier Architecture maintains Data Integrity. Since there is a
middle layer between the client and the server, data corruption can be
avoided/removed.
3.Security: 3-Tier Architecture Improves Security. This type of model
prevents direct interaction of the client with the server thereby reducing
access to unauthorized data.
Disadvantages of 3-Tier Architecture:
1.More Complex: 3-Tier Architecture is more complex in comparison to 2-Tier
Architecture. Communication Points are also doubled in 3-Tier Architecture.
2.Difficult to Interact: It becomes difficult for this sort of interaction to take
place due to the presence of middle layers.

Q5. What are the different data models used in database systems?
Introduction: (out of 9 write only 4 to 5)
Data models can be likened to architectural blueprints that underpin the
construction of a well-designed database. They offer a systematic database
approach to conceptualizing, defining, and categorizing data, allowing for a
comprehensive view of how data elements relate to one another.
Following are the various types of data models:
1. Hierarchical Data Model: Drawing inspiration from the structure of a tree,
the hierarchical data model arranges data in a hierarchical manner, akin to a
parent-child relationship. This model was prominent in early mainframe
databases, offering a simplistic yet hierarchical organization.
2. Network Data Model: Evolved from the hierarchical model, the network
data model introduces more complex relationships. Data elements are
interconnected in a mesh-like structure, permitting entities to possess multiple
parent and child records. This flexibility facilitates intricate data representation.
3. Relational Data Model: The stalwart of modern database systems, the
relational data model leverages the power of tables to represent data. Each
table comprises rows and columns, with relationships established through
keys. The structured nature of this model paved the way for the
ubiquitous SQL language.
4. Entity-Relationship (ER) Model: Stepping into the realm of conceptual
design, the ER model emphasizes entities, their attributes, and the
relationships between them. It employs entities to represent real-world objects
and illustrates how they interact, providing a blueprint for database schema
design.
5. Object-Oriented Data Model: Catering to the complexities of modern
applications, the object-oriented data model introduces the concept of
encapsulation. It models data as objects, encapsulating both attributes and
behaviors, thus mirroring real-world scenarios more accurately.
6. Object-Relational Data Model (ORDBMS): Blurring the boundaries
between the relational and object-oriented worlds, the ORDBMS integrates
object-oriented features into the relational model. This fusion accommodates
the storage of complex data types and encourages more expressive data
representation.
7. XML Data Model: With the rise of semi-structured data, the XML data
model shines as an adept choice. It is tailored for storing and representing
hierarchical data structures, making it invaluable for scenarios where flexibility
in schema design is essential.
8. NoSQL Data Models: Breaking free from the confines of tabular relations,
NoSQL databases embrace various data models, including key-value,
document, column-family, and graph models. These models cater to diverse
needs, such as high-speed data retrieval and flexible data structures.
9. Data Warehouse Models: Diving into the realm of business intelligence,
data warehouse models focus on optimizing data for analytical purposes.
Notable examples include the star schema and snowflake schema, which
facilitate efficient querying and reporting.