DBMS
DBMS
Database: A database is a collection of interrelated data that helps in the efficient retrieval,
insertion, and deletion of data from the database and organizes the data in the form of tables,
views, schemas, reports, etc. For Example, a university database organizes the data about
students, faculty, admin staff, etc. which helps in the efficient retrieval, insertion, and deletion of
data from it.
o It can provide a clear and logical view of the process that manipulates data.
o DBMS contains automatic backup and recovery procedures.
o It contains ACID properties which maintain data in a healthy state in case of failure.
o It can reduce the complex relationship between data.
o It is used to support manipulation and processing of data.
o It is used to provide security of data.
o It can view the database from different viewpoints according to the requirements of the
user.
Advantages of DBMS:
2. NoSQL DBMS: Designed for high-performance scenarios and large-scale data, NoSQL
databases store data in various non-relational formats such as key-value pairs, documents,
graphs, or columns. Examples are NoSQL DBMS are MongoDB, Cassandra, DynamoDB
and Redis.
4. Network DBMS: It is the database that typically follows the network data model. Here,
the representation of data is in the form of nodes connected via links between them.
Unlike the hierarchical database, it allows each record to have multiple children and
parent nodes to form a generalized graph structure.
5. Hierarchical DBMS: It is the type of database that stores data in the form of parent-
children relationship nodes. Here, it organizes data in a tree-like structure.
Database design and architecture: Creating the structure and layout of databases to ensure
they are optimized for performance and scalability. A DBA is involved in creating the structure
of the database (tables, relationships, views, etc.), ensuring it is designed to meet the
organization’s needs efficiently.
The DBA ensures that the database design avoids redundancy and follows normalization
principles. They also optimize the design for performance, scalability, and data integrity.
The DBA installs and configures the database management system (DBMS), such as MySQL,
Oracle, or SQL Server, based on the organization’s needs.
Backup and recovery: Ensuring that regular backups are taken, and planning and
implementing disaster recovery strategies to safeguard data.
The DBA is responsible for establishing and executing regular database backup schedules to
prevent data loss in case of system failures or disasters
Data integrity and maintenance: Ensuring the integrity, accuracy, and consistency of data
stored in the database over time.
A DBA can work with various types of databases, including relational (e.g., MySQL,
PostgreSQL, Oracle) or NoSQL databases (e.g., MongoDB, Cassandra). The role is crucial for
any organization that relies on databases for their operations.
DBMS Architecture:
o The DBMS design depends upon its architecture. The basic client/server architecture is
used to deal with a large number of PCs, web servers, database servers and other
components that are connected with networks.
o DBMS architecture depends upon how users are connected to the database to get their
request done.
Database architecture can be seen as a single tier or multi-tier. But logically, database
architecture is of two types like: 2-tier architecture and 3-tier architecture.
o In this architecture, the database is directly available to the user. It means the user can
directly sit on the DBMS and uses it.
o The 1-Tier architecture is used for development of the local application, where
programmers can directly communicate with the database for the quick response.
o Any changes done here will directly be done on the database itself.
Advantages of 1-Tier Architecture
• Simple Architecture: 1-Tier Architecture is the most simple architecture to set up, as only
a single machine is required to maintain it.
• Cost-Effective: No additional hardware is required for implementing 1-Tier Architecture,
which makes it cost-effective.
• Easy to Implement: 1-Tier Architecture can be easily deployed, and hence it is mostly
used in small projects.
3-Tier Architecture
o The 3-Tier architecture contains another layer between the client and server. In this
architecture, client can't directly communicate with the server.
o The application on the client-end interacts with an application server which further
communicates with the database system.
o The 3-Tier architecture is used in case of large web application.
1. Physical Schema: This describes how data is stored physically on the storage medium. It
includes the structure of files, how the data is indexed, how tables are partitioned, and
other low-level storage details.
Database
The three schema architecture is also used to separate the user applications and physical
database.
The three schema architecture contains three-levels. It breaks the database down into three
different categories.
In the conceptual level, internal details such as an implementation of the data structure are
hidden.
Programmers and database administrators work at this level.
At the external level, a database contains several schemas that sometimes called as subschema.
The subschema is used to describe the different view of the database.
This is the highest level of data abstraction which describes the interaction between the user and
the system. It permits the users to access data in a way that is customized according to their
needs, so that the same data can be seen by different users in different ways, at the same time.
The main objective of three level architecture is to enable multiple users to access the same data
with a personalized view while storing the underlying data only once. Thus it separates the user's
view from the physical structure of the database. This separation is desirable for the following
reasons:
o Logical data independence refers characteristic of being able to change the conceptual
schema without having to change the external schema.
o Logical data independence is used to separate the external level from the conceptual
view.
o If we do any changes in the conceptual view of the data, then the user view of the data
would not be affected.
o Logical data independence occurs at the user interface level.