Da Tabase Management System: Hassan Khan
Da Tabase Management System: Hassan Khan
Da Tabase Management System: Hassan Khan
MANAGEMENT SYSTEM
HASSAN KHAN
Database
• Database is a collection of related data and data is a collection of facts
and figures that can be processed to produce information.
Designers −
• Designers are the group of people who actually work on the designing part of the database.
They keep a close watch on what data should be kept and in what format. They identify and
design the whole set of entities, relations, constraints, and views.
End Users −
• End users are those who actually reap the benefits of having a DBMS. End users can range from
simple viewers who pay attention to the logs or market rates to sophisticated users such as
business analysts
DBMS vs. File System
There are following differences between DBMS and File system:
DBMS File System
DBMS is a collection of data. In DBMS, the user is not File system is a collection of data. In this system, the user has to
required to write the procedures. write the procedures for managing the database.
DBMS gives an abstract view of data that hides the details. File system provides the detail of the data representation and
storage of data.
DBMS provides a crash recovery mechanism, i.e., DBMS File system doesn't have a crash mechanism, i.e., if the system
protects the user from the system failure. crashes while entering some data, then the content of the file will
lost.
DBMS provides a good protection mechanism. It is very difficult to protect a file under the file system.
DBMS contains a wide variety of sophisticated techniques to File system can't efficiently store and retrieve the data.
store and retrieve the data.
DBMS takes care of Concurrent access of data using some In the File system, concurrent access has many problems like
form of locking. redirecting the file while other deleting some information or
updating some information.
DBMS Architecture
• A 3-tier architecture separates its tiers from each other based on the
complexity of the users and how they use the data present in the
database. It is the most widely used architecture to design a DBMS.
3-tier Architecture (Continue)
• Database (Data) Tier − At this tier, the database resides along with its query processing languages.
We also have the relations that define the data and their constraints at this level.
• Application (Middle) Tier − At this tier reside the application server and the programs that access
the database. For a user, this application tier presents an abstracted view of the database. End-
users are unaware of any existence of the database beyond the application. At the other end, the
database tier is not aware of any other user beyond the application tier. Hence, the application
layer sits in the middle and acts as a mediator between the end-user and the database.
• User (Presentation) Tier − End-users operate on this tier and they know nothing about any
existence of the database beyond this layer. At this layer, multiple views of the database can be
provided by the application. All views are generated by applications that reside in the application
tier.