Chapter 2: Database System Concepts

and Architecture

Database Systems CS203

Week 02
3rd-Sep-2018

By: Anam Qureshi

Outline
• Data Models and Their Categories
• Schemas, Instances, and States
• Three-Schema Architecture
• Data Independence
• Database Languages and Interfaces
• Database System Environment
• Database System Tools
• Centralized and Client-Server Architecture
• Classification of DBMSs
Data Model
Data Model
• Data Model:
 A set of concepts to describe the structure of a database,
the operations for manipulating these structures, and
certain constraints that the database should obey.
• Data Model Structure and Constraints:
 Constructs are used to define the database structure
 Constructs typically include elements (and their data
types) as well as groups of elements (e.g. entity, record,
table), and relationships among such groups
 Constraints specify some restrictions on valid data; these
constraints must be enforced at all times
Categories of Data Models
Categories of Data Models

High-level or Conceptual data models

Low-level or Physical data models

Representational data models

Self-describing data models

Database Schema
Database Schemas
 Database Schema:
• The description of a database.
• Includes descriptions of the database
structure, data types, and the constraints on
the database.
 Schema Diagram:
• An illustrative display of (most aspects of) a
database schema.
 Schema Construct:
• A component of the schema or an object
within the schema, e.g., STUDENT, COURSE.
Example of a Database Schema
Database Instance
Database Instances
 Database State:
• The actual data stored in a database at a
particular moment in time. This includes the
collection of all the data in the database.
• Also called database instance (or occurrence
or snapshot).
 The term instance is also applied to
individual database components, e.g.
record instance, table instance, entity
instance
Database Instances/States

Database
State

Empty Initial Valid

State State State
Database Schema Vs Database State

• Distinction
 The database schema changes very
infrequently.
 The database state changes every time the
database is updated.

• Schema is also called intension.

• State is also called extension.
Example of a Database State
Three-Schema Architecture
Three-Schema Architecture

• Proposed to support DBMS characteristics

of:
 Program-data independence.
 Support of multiple views of the data.
• Not explicitly used in commercial DBMS
products, but has been useful in explaining
database system organization
Three-Schema Architecture
Three-Schema Architecture

• Defines DBMS schemas at three levels:

 Internal schema at the internal level to describe physical
storage structures and access paths (e.g indexes).
 Typically uses a physical data model.
 Conceptual schema at the conceptual level to describe
the structure and constraints for the whole database for a
community of users.
 Uses a conceptual or an implementation data model.
 External schemas at the external level to describe the
various user views.
 Usually uses the same data model as the conceptual
schema.
Mappings
• Mappings among schema levels are needed to
transform requests and data.
 Programs refer to an external schema, and
are mapped by the DBMS to the internal
schema for execution.
 Data extracted from the internal DBMS level is
reformatted to match the user’s external view
(e.g. formatting the results of an SQL query for
display in a Web page)
Data Independence
Data Independence

Data
Independence

Logical Data Physical Data

Independence Independence
DBMS Languages
DBMS Languages

DDL

DBMS
DML SDL
Languages

VDL
Data Definition Language DDL

• Data Definition Language (DDL):

 Used by the DBA and database designers to specify
the conceptual schema of a database.
 In many DBMSs, the DDL is also used to define
internal and external schemas (views).
 In some DBMSs, separate storage definition
language (SDL) and view definition language (VDL)
are used to define internal and external schemas.
 SDL is typically realized via DBMS commands
provided to the DBA and database designers
Data Manipulation Language DML

• Data Manipulation Language (DML):

 Used to specify database retrievals and updates
 DML commands (data sublanguage) can be
embedded in a general-purpose programming
language (host language), such as COBOL, C,
C++, or Java.
 A library of functions can also be provided to
access the DBMS from a programming language
• Alternatively, stand-alone DML commands can be
applied directly (called a query language).
Types of DML

• High Level or Non-procedural Language:

 For example, the SQL relational language
 Are “set”-oriented and specify what data to retrieve
rather than how to retrieve it.
 Also called declarative languages.
• Low Level or Procedural Language:
 Retrieve data one record-at-a-time;
 Constructs such as looping are needed to retrieve
multiple records, along with positioning pointers.
DBMS Interfaces
DBMS Interfaces

Menu-based Apps for Mobile Forms-based

Interfaces Devices Interfaces

Natural Keyword-based
Graphical User
language Database
Interfaces
Interfaces Search

Interfaces for
Speech Input Interfaces for
Parametric
and Output the DBA
Users
The Database System
Environment
Typical DBMS Component Modules
Reading Assignment

2.4.2 Database System Utilities

2.4.3 Tools, Applications, Environments, and
Communication Facilities
Centralized and Client/Server
Architecture for DBMSs
Centralized DBMS
• Centralized DBMS:
 Combines everything into single system
including- DBMS software, hardware,
application programs, and user interface
processing software.
 User can still connect through a remote
terminal – however, all processing is done at
centralized site.
A Physical Centralized Architecture
Basic 2-tier Client-Server Architectures

• Specialized Servers with Specialized functions

 Print server
 File server
 DBMS server
 Web server
 Email server
• Clients can access the specialized servers as
needed
Logical 2-Tier Client Server Architecture
Clients
• Provide appropriate interfaces through a client
software module to access and utilize the various
server resources.
• Clients may be diskless machines or PCs or
Workstations with disks with only the client
software installed.
• Connected to the servers via some form of a
network.
 (LAN: local area network, wireless network,
etc.)
DBMS Server

• Provides database query and transaction

services to the clients
• Relational DBMS servers are often called SQL
servers, query servers, or transaction servers
• Applications running on clients utilize an
Application Program Interface (API) to access
server databases via standard interface such as:
 ODBC: Open Database Connectivity standard
 JDBC: for Java programming access
3-Tier Client-Server Architecture
• Common for Web applications
• Intermediate Layer called Application Server or Web
Server:
 Stores the web connectivity software and the business
logic part of the application used to access the
corresponding data from the database server
 Acts like a conduit for sending partially processed data
between the database server and the client.
• Three-tier Architecture Can Enhance Security:
 Database server only accessible via middle tier
 Clients cannot directly access database server
 Clients contain user interfaces and Web browsers
 The client is typically a PC or a mobile device connected to
the Web
3-tier client-server architecture
Classification of DBMSs
 Classification of DBMSs

Classification
of DBMSs

Based on Data Other

Model Classifications

Recent
Legacy Currently Used Single-User Multiple-User Centralized Distributed
Technologies

Object-
Network Hierarchical Relational NOSQL Homogeneous Heterogeneous
Oriented
Cost Considerations for DBMSs

 Cost Range: from free open-source systems to

configurations costing millions of dollars
 Examples of free relational DBMSs: MySQL,
PostgreSQL, others
 Commercial DBMS offer additional specialized modules,
e.g. time-series module, spatial data module, document
module, XML module
 These offer additional specialized functionality when
purchased separately
 Sometimes called cartridges (e.g., in Oracle) or blades
 Different licensing options: site license, maximum
number of concurrent users (seat license), single user,
etc.
Other Considerations

 Type of access paths within database system

 E.g.- inverted indexing based (ADABAS is one such
system).Fully indexed databases provide access by
any keyword (used in search engines)
 General Purpose vs. Special Purpose
 E.g.- Airline Reservation systems or many others-
reservation systems for hotel/car etc. Are special
purpose OLTP (Online Transaction Processing
Systems)
Chapter Summary

• Data Models and Their Categories

• Schemas, Instances, and States
• Three-Schema Architecture
• Data Independence
• DBMS Languages and Interfaces
• Database System Utilities and Tools
• Database System Environment
• Centralized and Client-Server Architectures
• Classification of DBMSs