DATABASE MANAGEMENT S Y S T E M S

UNIT : 1
DATABASES AND DATABASE U S E R S
Outline
 Introduction
 Characteristics of the Database Approach
 Actors on the Scene
 Workers behind the Scene
 Advantages of Using D B M S Approach
 A Brief History of Database Applications
 When Not to Use a D B M S
 Database System Concepts and Architecture
 Data Models, Schemes and Instances
 Three-Schema Architecture and Data Independence
 Database Languages and Interfaces
 The Database System Environment
 Centralized and Client-Server Architectures
 Classification of Database Management Systems
Data
Data is Raw of Facts
Data are facts, set of symbols to represent objects, events, activities
and quantities. Data can be considered as the raw material
information.
Data can be classified as:
Fact - e.g., Price of a printer
Event - e.g., arrival of new stock, or a patient has reported to
the doctor’s receptionist
Transaction – e.g., making a booking

Database
A database is an integrated collection of logically related records and
files. It consolidates records previously stored in independent files so
that data be accessed by many application programs.
 Database System
Database system gives centralized control over the database. The
database system is created and maintained either by a group of
application programs written specification for that task or by a
Database Management System (DBMS).

Some important Properties:

• A random collection of data can be said as a database. It is a
logically interrelated collection of Data.

• Database contains only data, no information.

• Database is flexible and can store huge quantity of data

 Types of Database
There are two types of Database on their functionality and their
location
Database

Centralized Database Distributed Database

 Characteristics of Database System
Database management systems were developed to handle the
following difficulties of typical file-processing systems supported by
conventional operating systems:
• Data redundancy and inconsistency
• Difficulty in accessing data
• Data isolation – multiple files and formats
• Integrity problems
• Atomicity of updates
• Concurrent access by multiple users
• Security problems
• Data Independence and Data Integrity
• Ease of Learning & Use
• More Information at Low Cost
• Recovery from Failure
• Data Sharing and Security
 Key Terms of Database System
There are three important terms used in Database are:
Field: Fields contain one piece of information of entry.
Ex: In an address book each entry has fields for First name,
last name, address, ph no., email, etc.
Record: One full set of fields i.e., all related information about one
person or object is called Record.
Ex: An address book all the information for first person is one
record
Table: A complete collection of records is called a table. A table
contains rows and columns.
Each column of a table represents Field and
Each row represents Record
 ACTOR ON THE SCENE
The main aim of database is to provide an environment for storing and
accessing data in a more secured and efficient way. Once it is created, it
can be used by the use of various ways. Depending on its use, the actors
on scene or actuals users are classified in following four categories:
Database System Users / Workers Behind the Scene
1. Database Administrator (DBA): Database Administrator is
administrating the database and the secondary resources. The job of
a plan, design, create, modify and maintain the database with
special emphasis on security and integrity.
2. Database Designer: The designer are identifying the data to be
stored in the database and choosing appropriate structures to
represent and store those data.
3. End User: The job of end user is to access the database for
querying, updating and generating reports. End users are:
Casual, Naïve or Parametric,
Sophisticated and stand alone user
4. System Analysis & Application Programmers: Application
programmers implements those specifications as programs, then
testing, debugging, documenting and maintaining.
5. Application Programmers: These users write application programs
to interact with the database. Application programs can be written in
some programming language such as C++, JAVA or some higher level
fourth generation language.
6. Operators and Maintenance Personnel: They are responsible for
the actual running and maintenance of the hardware and software
environment for the database system.
7. DBMS System Designers: They implement the DBMS modules
and interfaces as a software package. A DBMS is a very complex
software system that consists of many components or modules,
including modules for implementing the catalogue, query language
processing, interface processing, accessing and buffering data,
handling data recovery and security.
8. Tool Developers: They design and implement tools. The software
packages that facilitate database modeling and design, database system
design and improved performance. Tools are optional packages that are
often purchased separately.
 Database Administrator
• Coordinates all the activities of the database system; the
database administrator has a good understanding of the
enterprise’s information resources and needs:
• Database administrator’s duties include:
– Schema definition
– Storage structure and access method definition
– Schema and physical organization modification
– Granting user authority to access the database
– Specifying integrity constraints
– Acting as liaison with users
– Monitoring performance and responding to changes in
requirements
 DATABASE LANGUAGES

DDL DML DCL TCL

Data Data Data Transaction

Definition Manipulation Control Control
Language Language Language Language
 DATABASE LANGUAGES
Instances: The collection of information stored in the database at a particular
moment is called an Instances of Database.
Schema: The overall design of the database is called schema.
Database languages are 4 types. They are:
1. Data Definition Language (DDL)
A database is specified by a set of definitions expressed by a language called DDL.
This language contains commands used to create and destroy databases and
database objects. DDL statements is a set of tables that is stored in a special file
called Data Dictionary.
DDL commands are:-
CREATE: To create objects in the Database.
ALTER: Alters the structure of the Database.
DROP: Delete objects from the Database.
TRUNCATE: Remove all records from a table, including all space
allocated for the records are removed.
COMMENT: Add comments to the data dictionary.
RENAME: Rename an object.
2. Data Manipulation Language (DML)
A data Manipulation Language (DML) is a language that enables
users to access or maintain data as organized by the appropriate
database systems. These commands will be used by all database
users during the routine operation of the database. The DML
statements are used for managing data within schema objects.
DML commands are:
SELECT – Retrieve data from the a database.
INSERT – Insert data into a table.
UPDATE – Updates existing data within a table.
DELETE – Deletes all records from a table, the space for the records remain.
MERGE – UPSERT operation (Insert or Update)
CALL – Call a PL/SQL or Java Subprogram.
EXPLAIN PLAN – Explain access path to data.
LOCK TABLE – Control Concurrency.
3. Data Control Language (DCL)
A Data Control Language (DCL) is a computer language and a subset of SQL,
used to control access to data in a database.
DCL commands are:
GRANT: Gives user’s access privileges to database.
REVOKE: Withdraw access privileges given with the GRANT command.

4. Transaction Control (TCL)

Transaction Control (TCL) statements are used to manage the changes made by
DML statements. It allows statements to be grouped together into logical
transactions.
TCL commands are:
COMMIT: Save work done.
SAVEPOINT: Identify a point in a transaction to which you can later roll back
ROLLBACK: Restore database to original since the last COMMIT.
SET TRANSACTION: Change transaction options like isolation level & what
rollback segment to use.
 Types of Database Management System /
Database Models
Every database system logically organizes data with respect to some
model called “Data Model”. A data model describes how various
pieces of data in the database are logically related to each other. The
data model represents the relationship between the entities. The
database model is also called as “Database Architecture”.
 1. HIERARCHICAL DATABASE MODEL
 Files are arranged in a top-down structure that resembles a tree or
genealogy chart.
 The Top file is called the ROOT, The Bottom files are called
Leaves & Intermediate files have one parent or owner file & one
or several children files.
 Hierarchical database technology is used for high-volume
transaction processing & MIS (Management Information System)
Application.
 Assumes data relationships are hierarchical
 One-to-Many (1:M) relationships
 Each parent can have many children
 Each child has only one parent
 Logically represented by an upside down tree
 ADVANTAGES
 It is the easiest model database
 A database owner is more secured because nobody else can see
& modify a child without consulting to its parent.
 Searching is fast & easy, if parent is known.
 Very efficient in handing ‘one-to-many’ relationship.

 DISADVANTAGES
 It is old fashioned, outdated database model.
 Modification & addition of child without consulting the parent is
impossible or very hard. So, it is non-flexible database model.
 Can’t handle ‘many-to-many’ relationship.
 Increases redundancy because same data is to be written in
different places.
 Deleting a parent from the database deletes all the children.
 2. NETWORK DATABASE MODEL
 Similar to Hierarchical Model
 Records linked by pointers
 Composed of sets
 Each set consists of owner (parent) and member (child)
 Many-to-Many (M:N) relationships representation
 Each owner can have multiple members (1:M)
 A member may have several owners
 In this model, each file may be associated with an arbitrary number
of files.
 Network model systems are still popular on powerful mainframes
& for high-volume transaction processing applications.
 Since the database designer has such detailed control over data
organizations, it is possible to design highly optimized database
with network systems.
 ADVANTAGES
 More flexible than hierarchical because accepts many-to-many
relationship.
 Reduces redundancy because data shouldn’t be repeated if same type of
data is needed. For such case, a parent can have more than one virtual
parents & one real parent.

 Searching is faster because of multidirectional pointers.

 DISADVANTAGES
 Very complex type of database model.
 Needs long programs to handle the relationship.
 Pointers needed in the database model increases overhead of storage.
 Less security in comparison to hierarchical model, because it is open to
all.
 3. Relational Model
 E. F. Codd’s Relational Model proposal
 Separated the notion of physical representation (machine-view)
from logical representation (human-view)
 Considered ingenious but computationally impractical in 1970
 Relational Database Model
 Dominant database model of today
 Eliminated pointers and used tables to represent data
 Tables
 flexible logical structure for data representation
 A series of row/column intersections
 related by sharing common entity characteristic(s)
The relational model is the most recent of the three database structures. It
was developed in an attempt to simplify the representation of relationships
among data elements in large database.
Provides a logical “human-level” view of the data & associations
among groups of data (i.e., tables)

Customer_ID Customer_Account Agent_ID

1224 4556 23
1225 4558 25

Agent_ID Last_Name First_Name Phone

23 Sturm David 334-5678
25 Long Kyle 556-3421

Customer_ID Last_Name First_Name Phone Account_Balance

1224Vira Dyne 678-9987 1223.95
1225Davies Tricia 556-3342 234.25
 Advantages
o Structural Dependence
 Separation of database design and physical data storage/access
 Easier database design, implementation, management, and use
o Ad hoc query capability with Structured Query Language (SQL)
 SQL translates user queries to codes

 Disadvantages
o Substantial hardware and system software overhead
 more complex system
o Poor design and implementation is made easy
 ease-of-use allows careless use of RDBMS
 4. OBJECT ORIENTED MODEL
 Object-oriented concepts became popular in 1990s
 Modularity facilitated program reuse and construction of complex
structures
 Ability to handle complex data types (e.g. multimedia data)
 Object-Oriented Database Model (OODBM)
 Maintains the advantages of the ER model but adds more features
 Object = entity + relationships (between & within entity)
 consists of attributes & methods
o describe properties of an object
o are all relevant operations that can be performed on an object
 self-contained abstraction of real-world entity
 Class = collection of similar objects with shared attributes and methods
 e.g. EMPLOYEE class = (employ1 object, employ2 object, …)
 organized in a class hierarchy
o e.g. PERSON > EMPLOYEE, CUSTOMER
 Incorporates the notion of inheritance
 attributes and methods of a class are inherited by its descendent
classes
CHARACTERISTICS OF THE DATABASE APPROACH
 Self-describing nature of a database system:
 A DBMS catalog stores the description of a particular database (e.g. data
structures, types and constraints)
 The description is called meta-data.
 This allows the DBMS software to work with different database
applications.
 Insulation between programs and data:
 Called program-data independence.
 Allows changing data structures and storage organization without having to
change the DBMS access programs.
 Creation, modification and deletion of data files.
 Addition, modification, deletion of data.
 Retrieving of data collectively or selectively.
 Sorting or indexing of data.
 Creation of input forms and output reports.
 Manipulation of stored data.
 To support concurrent transactions.
 To maintain data integrity and security.
 To create an environment for data warehousing and data mining.
 Sharing of data and Multi-user transaction Processing.
Database Management System (DBMS)
• Collection of interrelated data and a set of programs to
access those data.
• DMBS contains information about a particular enterprise
• DBMS provides an environment that it both convenient
and efficient to use in retrieving and storing database
information
• DBMS acts as the interface between the application
programs and the Database.
Some of the DBMS Packages:
 MS-Access
 My SQL
 SyBASE
 Oracle
 Fox Pro
Database System with DBMS
Contd…
 It ensures data security.
 It ensures conflict resolution.
 It restrict unauthorized access.
 It can be used to provide persistent storage for program objects
and data structures.
 It provides storage structures and search techniques for efficient
query processing.
 It helps in providing multiple user interfaces.
 It represent complex relationships among data.
 It allows data sharing.
 It ensures data integrity.
A BRIEF HISTORY OF DATABASE APPLICATIONS
One of the most important purposes of development of computer
systems was the database application which could have been used on
them. Data processing drove growth of computer processor speed.
In fact, data processing predates the computers; punched cards
were used in the US for collecting data for census during beginning of
20th century. Earliest data processing was done by punched cards on
mechanical devices. The real development in data processing speed,
storage of data and development of DB applications started much
later i.e. from 1950s.
Magnetic tapes were used to store data and being read from it.
These database applications had hierarchical structure and used
network systems. They were extremely efficient when used with the
original query, exactly developed for them, but the DB was not
designed to handle new queries or transactions. Also the magnetic
tapes must be in same sorted order so as to retrieve the authentic data.
 Later in 60s hard disks came about and data retrieval was faster
and did not need be stored sequentially. This period was also
remarkable in terms of advancement in DB Systems.
 Later in 1970 Edgar Codd, father or Relational Database Model,
conceptualized a new structure for Database construction and
wrote a groundbreaking paper ‘A Relational Model of Data for
Large Shared Data Banks’.
 He freed database from procedural ways of querying and marked
the beginning of Data Abstraction i.e. hiding details of how
Database is implemented to application programmers and end
users.
 System R, based on Codd’s concept was developed by IBM and it
was first to have a language for querying called SQL or Structured
Query Language.
 Later, System R was further developed to a mainstream
commercial DBMS product known as DB2.
 Object oriented programming was rapidly developing in the 80s
and it also helped break into what we know as Object Oriented
Databases. The idea was to treat data as objects and it became
easier to conceptualize and program using this idea.
 Another great development which happened was processing speed
of processors and also conceptualization of indexing which greatly
increased data access times, and performances of DB.
 90s was a time of a World Wide Web, so unprecedented like world
had never seen before. The data was here on the internet.
Databases to which links were forwarded were varied and different
and it needed a technique to interchange data efficiently.
 Also the database had to be of very high availability working 24x7.
XML or eXtended Markup Language is a standard for providing
data exchange among different databases and Webpages.
 More recently, there has been a growing trend of NoSQL database.
These are different from so called classical databases and do not
rely on Relational Model for their structure.
 They do not query data using Structured Query Language but
UnQL or Unstructured Query Language which is still in
development stage (it is similar to XQuery).
 These databases are generally used when working with huge
quantities of data. Some examples are Mongo DB, CouchBase,
HBase used by facebook, Big Table used by Google and Dynamo
DB used by Amazon.
WHEN NOT TO USE A DBMS
The DBMS should not be used due to the following reasons:
 If the database and applications are simple, well defined and not
expected to change.
 If there are stringent real-time requirements that may not be met
because of DBMS overhead.
 If access to data by multiple users is not required.
 Due to the high initial investment in hardware, software and
training.
 Due to the generality that a DBMS provides for defining and
processing data.
 Overhead for providing security, concurrency, control, recovery
and integrity functions.
 Due to embedded systems with limited storage capacity.
 When DBMS would not fit.
 DATA MODELS
The collection of conceptual tools for describing data, data relationships,
data semantics and consistency constraints is called Data Model.
FEATURES OF DATA MODELS
 It’s a type of data abstraction. It supports data abstraction so that different
users can perceive data at their preferred level of detail.
 It provides the necessary means to achieve this abstraction.
 The structure of a database includes the data types, relationships and
constraints that apply to the data.
 It includes a set of basic operations for specifying retrievals and updates
on the database in addition to the basic operations provided by the data
model.
 It includes concepts to specify the dynamic aspect or behavior of a
database applications.
 It allows the database designer to specify a set of valid user-defined
operations.
 It allows the database objects such as generic operations to insert, delete,
modify or retrieve any kind of object.
 CATEGORIES OF DATA MODELS
A Data Model in Database Management System (DBMS), is the
concept of tools that are developed to summarize the description of the
database. It is classified into 3 types:

1. Conceptual Data Model :

Conceptual data model, describes the database at a very high level
and is useful to understand the needs or requirements of the
database. It is this model, that is used in the requirement gathering
process i.e., before the Database Designers start making a particular
database. One such popular model is the entity / relationship model
(ER Model). The E/R model specializes in entities, relationships
and even attributes which are used by the database designers.
 In terms of this concept, a discussion can be made even with non-
computer science(non-technical) users and stakeholders, and their
requirements can be understood.
2. Representational Data Model :
This type of data model is used to represent only the logical part of
the database and does not represent the physical structure of the
databases. The representational data model allows us to focus
primarily, on the design part of the database. A popular
representational model is Relational Model.
3. Physical Data Model :
Ultimately, all data in a database is stored physically on a
secondary storage device such as discs and tapes. This is stored in
the form of files, records and certain other data structures. It has all
the information of the format in which the files are present and the
structure of the databases, presence of external data structures and
their relation to each other.
 SCHEMAS and INSTANCES
Instances:
Instances are the collection of information stored at a particular
moment. The instances can be changed by certain CRUD operations
as like addition, deletion of data. It may be noted that any search
query will not make any kind of changes in the instances.
Example
Let’s say a table teacher in our database whose name is School,
suppose the table has 50 records so the instance of the database has
50 records for now and tomorrow we are going to add another fifty
records so tomorrow the instance have total 100 records. This is
called an instance.
Schema:
Schema is the overall description of the database. The basic structure
of how the data will be stored in the database is called schema.
Schema is of three types: Logical
Schema, Physical Schema and view
Schema.
Logical Schema – It describes the
database designed at logical level.
Physical Schema – It describes the
database designed at physical level.
View Schema – It defines the design
of the database at the view level.
Example:
Let’s say a table teacher in our database name school, the teacher
table require the name, dob, doj in their table so we design a structure
as :
Teacher table name: String doj: date dob: date
 Three Schema Architecture of DBMS
1. Internal Level
2. Conceptual Level
3. External Level
Internal Level is that level ‘where the actual file is stored on the
disk’
External Level the user is concerned as to what data items are needed
and how these would be represented. The user is concerned only with
the required fields in the records. The user specifies his own view and
develops his program.
Conceptual Level It is the bridge between internal and external level.
This level has the information of all internal and external levels. This
level matches the requirements of user’s view (external level) with the
stored files and records therein.
DBMS LANGUAGES
 DATABASE INTERFACES
A DBMS interface is the abstraction of a piece of functionality of a DBMS.
It usually refers to the communication boundary between the DBMS and
clients or to the abstraction provided by a component within a DBMS. A
DBMS interface hides the implementation of the functionality of the
component it encapsulates.
 THE DATABASE SYSTEM ENVIRONMENT
Database system refers to a set of components that define and
control the collection, storage, management and use of data.
Centralized DBMS Architecture
 Centralized databases are the traditional database systems
where all database functionality, data, application program
and user interface processing are located on one machine.
Access to the database from remote locations is via the
communication links
 In the early systems, the mainframe computers provided all
the functionality required by the users of computer.
The users interacted with the mainframe computers
via dumb terminals. All processing was performed on the
mainframe computer. The DBMS was centralized, and stored
on the mainframes. The dumb terminals had only the display
facility.
 The centralized database is easy to manage and administer.
 Common examples of centralized databases are personal
database, and central computer database.
Client-Server Architecture
 The growth of Personal Computer (PC) has resulted in PCs
replacing the dumb terminals. PCs are powerful and fast
machines that can handle the user interface functionality.
 Client-Server systems involve a client machine and a server
machine. Clients are PCs or workstations that have user
interface capability and functionality for local processing.
Servers are powerful computers that can manage the files
(file servers), printer (printer servers), or, e- mails (e-mail
servers).
The client is connected to the server via a
communication link. The client interacts with the server
when it requires access to any additional functionality that
does not exist in its own machine. Client provides interfaces
to access and utilize the server resources.
 The Client-Server architecture has three components—the
user interface programs, the application programs that contain
the application logic, and the DBMS that stores the data. The
request made by the user interface program is processed using
the application logic which then accesses the database to
retrieve the data.
 The DBMS architecture on the Client-Server systems are of
two kinds: two-tier Client-Server architecture and three-tier
Client-Server architecture.
 In two-tier Client-Server architecture, the user interface
programs and the application programs run on the client side.
An Application Program Interface (API) allows client side
programs, to call the DBMS which is at the server side. The
client programs use Open Data Base Connectivity (ODBC) or
Java Data Base Connectivity (JDBC) interfaces to
communicate with the database.
 The three-tier Client-Server architecture is commonly used for
web applications. In addition to the client and the database
servers, it has an intermediate layer or middleware called
Application Server or Web Server.
 The web server stores the application or business logic part
of the application.
 The client stores the user interface. The DBMS is stored at
the server side. The web server interacts with client at one
end, and with the server for the DBMS at the other end.
 The web server acts like a pipe for receiving the client
request, processing it and accessing the data from the
DBMS server, and sending it back to the client. Figure
shows the two-tier and three-tier Client-Server architecture.
CLASSIFICATION O F DATABASE MANAGEMENT S Y S T E M S .
As we all know D B M S is an interesting subject and so is its classification.
There are several criteria based on which D B M S is classified. The
classification and types of Database Management System(DBMS) is
explained in a detailed manner below based on the different factors.
BASED ON THE DATA MODELs
1 . Hierarchical Database
These D B M S employ parent and child relationships to store the data.
Hierarchical D B M S is wide.
They store data in a tree-like structure so that it is easy to find and use.
Similarly, the configuration of the D B M S is present in the nodes of the
tree.
2 . Network DBMS
Network D B M S supports many-to-many relations which results in
complex database structures.
R D M Server is a major example of the network D B M S .
3 . Relational DBMS
Relational D B M S stores data using the database relationships in the form
of tables, also known as relations or tuples.
They do not support many to many relationships and have pre-defined
data types that they can support. They are the most popular D B M S type
in the industry.
Example: Oracle, My SQL , M S S Q L , etc.
4 . Object-Oriented Relational DBMS
This D B M S supports the storage of miscellaneous data types. They store
data in the form of objects.
The object h as attributes (i.e., name, id, gender, etc.) and the logic for
what needs to be done with the data. Example: PostgreSQL.
BASED ON THE NUMBER O F USERs
 Single user
As the name itself indicates it can support only one user at
a time. It is mostly used with the personal computer on
which the data resides accessible to a single person. The
user may design, maintain and write the database
programs.
 Multiple users
It supports multiple users concurrently. Data can be both
integrated and shared. A database should be integrated
when the same information is not need be recorded in two
places.
For example a student in the college should have the
database containing his information. It must be accessible
to all the departments related to him. For example the
library department and the fee section department should
have information about student’s database. So in such case,
we can integrate and even though database resides in only
one place both the departments will have the access to it.
 BASED ON THE S I T E S O V E R WHICH NETWORK IS
DISTRIBUTED
Centralized database system - The D B M S and database are
stored at the single site that is used by several other systems too.
We can simply say that data here is maintained on the centralized
server.

Parallel network database system - This system has the

advantage of improving processing input and output speeds.
Majorly used in the applications that have query to larger
database. It holds the multiple central processing units and data
storage disks in parallel.
Distributed database system - In this data and the D B M S
software are distributed over several sites but connected to the
single computer.

Further they are classified as

1.Homogeneous DBMS - They use same software but from the
multiple sites. Data exchange between the sites can be handled
easily. For example, library information systems by the same
vendor ,such as Geac Computer corporation, use the same
D B M S software that allows the exchanges between various Geac
library sites.
2.heterogeneous DBMS
They use different D B M S software for different sites but there is
a additional software that helps the exchange of the data
between the sites.
Client-server database system - This system has two logical
components namely client and server. Clients are generally the
personal computers or workstations whereas servers are the large
workstations, mini range computers or a main frame computer
system. The applications and tools of the D B M S run on the client
platforms and the D B M S software on the server.
Both server and client computers are connected over
the network. We can relate it to client and server in real life to
understand in a much better way. Here the applications and tools
act as a client send the requests for its services. The D B M S
processes these requests and returns the result to the client.
Server handles jobs that are common to many clients say database
access and updates.
Multi-tier client-server database system - The rise of personal
computers in business has increased the reliability of the network
hardware leading to evolution of two-tier and three-tier systems
which use different software for the client and software.
BASED ON THE C O S T
 Low cost DBMS - The cost of these systems vary from $100
to $3000. [Rs. 8000 to R s . 24000]
 Medium cost DBMS - Cost varies from $10000 to $100000.
[Rs. 800000 to R s. 8000000]
 High cost DBMS - Cost pf these systems are usually more
than $100000 . [Rs. 8000000]

BASED ON THE A C C E S S
This classification simply based on the access to data in the
database systems

 Sequential access - One after the other.

 Direct access
 Inverted file structures
BASED ON THE U S A G E
Online transaction processing (OLTP) DBMS
They manage the operational data. Database server must be able
to process lots of simple transactions per unit of time.
Transactions are initiated in real time, in simultaneous by lots of
user and applications hence it must have high volume of short,
simple queries.
Online analytical processing (OLAP) DBMS
They use the operational data for tactical and strategical
decision making. They have limited users deal with huge amount
of data, complex queries.
Big data and analytics DBMS
To cope with big data new database technologies have been
introduced. One such is NoSQL (not only SQL) which abandons
the well known relational database scheme.
X M L DBMS - two types
1. Native X M L DBMS - Use the logical, intrinsic structure of XML
document.
2. Enabled X M L DBMS - Existing D B M S with facilities to store XML
data and structured data in integrated way.
Multimedia DBMS - Stores data s u c h as text, images, audio, video
and 3D games which are usually stored in binary large object.
G I S DBMS - Stores and queries the spatial data.
Sensor DBMS - Allows to manage sensor data, bio-metric and
telematics data.

Mobile DBMS - Runs on the smartphones, tablets. It Handles the

local queries. Supports self management( no DBA).
Open source DBMS - Code is publicly available and can be extended
by anyone, popular for small business applications.