Chapter1_Introduction
Chapter1_Introduction
MANAGEMENT
SYSTEM
Subash Manandhar
1
Chapter 1 - Introduction
• Database
• Is a repository for collection of related data and facts.
• Is an organized collection of data so that it can be easily accessed and managed.
• Data and Information
• Data
• Is a raw, unorganized facts that need to be processed.
• Is meaningless and worthless.
• Information
• When data is processed, organized, structured or presented in a given context
so as to make it useful, it is called information.
• Is the output of data processing operation.
Subash Manandhar 2
Chapter 1 - Introduction
• DBMS
• Is a collection of programs that enables users to perform certain action on a
particular database.
• ‘Define’ the structure of database information.
• ‘Populate’ the database with appropriate information.
• ‘Manipulate’ the database.
• ‘Protect’ the database contents against accidental or deliberate corruption of
contents.
• ‘Share’ the database among multiple users.
• Is a software that defines a database, store data, supports a query language,
produce reports and creates data entry screen.
• Provide an environment that is both convenient and efficient to use in retrieving
and storing database information.
• Some examples are: ORACLE, MySQL, SQL SERVER, etc.
Subash Manandhar 3
Chapter 1 - Introduction
Subash Manandhar 4
Chapter 1 - Introduction
• Application areas :
• Banking
• Airlines
• Human Resources
• Education
• Hospitals
• E-commerce
• Sales
• Telecommunication
• Manufacturing
• etc.
Subash Manandhar 5
Chapter 1 - Introduction
• Objectives of DBMS :
• Providing mass storage of relevant data.
• Making easy access to data for authorized user.
• Providing prompt response to user’s request for data.
• Making the latest modification visible to all the database users immediately.
• Eliminating data redundancy.
• Allowing multiple users to be active at one time.
• Allowing the growth of database system.
• Providing data integrity.
• Protecting the data from physical harm and unauthorized access.
• Serving different types of users.
• Providing security with user access privilege.
• Combining inter-related data to generate report.
Subash Manandhar 6
Chapter 1 - Introduction
• Advantages of DBMS :
• Data sharing
• Reduced data redundancy
• Improved data integrity
• Increased security
• Time saving
• Report generation
• Disadvantages of DBMS :
• Costly
• Fast changing technology
• Requires trained manpower
• Chance of data leakage and hacking
Subash Manandhar 7
Chapter 1 - Introduction
• Evolution :
• 1960 - Charles Bachman designed first DBMS system
• 1970 - Codd introduced IBM'S Information Management System (IMS)
• 1976- Peter Chen coined and defined the Entity-relationship model also know as
the ER model
• 1980 - Relational Model becomes a widely accepted database component
• 1985- Object-oriented DBMS develops.
• 1990s- Incorporation of object-orientation in relational DBMS.
• 1991- Microsoft ships MS access, a personal DBMS and that displaces all other
personal DBMS products.
• 1995: First Internet database applications
• 1997: XML applied to database processing. Many vendors begin to integrate XML
into DBMS products.
• Recently, NoSQL databases came about as a response to the growth of the
internet and the need for faster speed and processing of unstructured data.
Subash Manandhar 8
Chapter 1 - Introduction
• Needs of DBMS
• Drawbacks of File System:
• Redundancy
• Inconsistency
• Maintenance Problem
• Difficulty in combining data
• Security
Subash Manandhar 9
Chapter 1 - Introduction
• RDBMS
• Relational Database Management System that is based on relational
model.
• ORDBMS
• Object Relational Database Management System that facilitates RDBMS
with additional support of Object Oriented Concepts.
Subash Manandhar 10
Chapter 1 - Introduction
• Data Abstraction
• Data abstraction hides details of data storage that are not needed by most
database users and applications.
• Ensures easy, smooth and efficient data structures in such a way that every
type of database user is able to access its desired information efficiently.
• Types of data abstraction
• Internal level (physical level)
• Conceptual level (logical level)
• External level (view level)
Subash Manandhar 11
Chapter 1 - Introduction
• Internal / Physical level :
• Is the lowest level of data abstraction that is close to physical storage.
• It describes :
• How data are actually stored in storage device?
• What will be storage techniques?
• Conceptual / Logical level :
• Is the next higher level.
• It describes :
• What data are actually stored in database?
• What are the relationships between data entities?
• External / View level :
• is close to the users.
• It describes:
• What is the way of viewing information to the concerned users?
Subash Manandhar 12
Chapter 1 - Introduction
View Level
Logical Level
Physical Level
Fig: Three levels of data
abstraction
Subash Manandhar 13
Chapter 1 - Introduction
• Data Independence
• Is the ability to modify a schema definition in one level without effecting a
schema definition in next high level.
• Each higher level of data architecture is immune to the changes of next
lower level of architecture.
• We can change the structure of a database without affecting data required
by users and programs.
• Two types of data independence:
• Physical data independence:
• Refers to the ability to modify the physical schema without affecting conceptual schema.
• Logical data independence:
• Refers to the ability to modify the conceptual schema without affecting view schema.
• It is more difficult to achieve than physical data independence because application
programs are dependent on logical structure of data that user access.
Subash Manandhar 14
Chapter 1 - Introduction
• Schema and Instances
• Schema
• Overall design of the database
• Instances
• The collection of information stored in database at particular moment.
• Physical Schema
• Is the database design at physical level of abstraction
• Logical Schema
• Is the database design at logical level of abstraction
• Subschemas
• Schemas at view level that describes different view of database.
Subash Manandhar 15
Chapter 1 - Introduction
• Schema and Instances
Fig : Schema
Fig : Instances
Subash Manandhar 16
Chapter 1 - Introduction
• Database Manager and Users
• DBA (Database Administrator)
• Creates or modify database schema, uses DDL
• responsible for providing security to the database and allows only the authorized
users to access/modify the data base.
• monitors the recovery and backup and provide technical support.
• Application Programmers
• Interact with database system through DML
• End User (Clients)
• Invoke one of the permanent application programs that have been written
previously.
Subash Manandhar 17
Chapter 1 - Introduction
• 1.8 Database Manager and Users
Subash Manandhar 18
Chapter 1 - Introduction
• Types of database
• Relational databases. Relational databases became dominant in the 1980s.
Items in a relational database are organized as a set of tables with columns and
rows. Relational database technology provides the most efficient and flexible
way to access structured information.
• Object-oriented databases. Information in an object-oriented database is
represented in the form of objects, as in object-oriented programming.
• Distributed databases. A distributed database consists of two or more files
located in different sites. The database may be stored on multiple computers,
located in the same physical location, or scattered over different networks.
• Data warehouses. A central repository for data, a data warehouse is a type of
database specifically designed for fast query and analysis.
• NoSQL databases. A NoSQL, or nonrelational database, allows unstructured
and semistructured data to be stored and manipulated (in contrast to a
relational database, which defines how all data inserted into the database must
be composed).
• NoSQL databases grew popular as web applications became more common and more
complex.
Subash Manandhar 19
Chapter 1 - Introduction
• Types of database
• Graph databases. A graph database stores data in terms of entities and the
relationships between entities.
• OLTP(Online Transaction Processing) databases. An OLTP database is a
speedy, analytic database designed for large numbers of transactions
performed by multiple users.
• Document/JSON database. Designed for storing, retrieving, and managing
document-oriented information, document databases are a modern way to
store data in JSON format rather than rows and columns.
Subash Manandhar 20