Scribd
Upload
7 views26 pages

Database Slides 5

Uploaded by

bilalbataineh011
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
7 views26 pages

Database Slides 5

Uploaded by

bilalbataineh011
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 26

Database System

Concepts and
Architecture
Ch.2
Data Models
• Data model
– Collection of concepts that describe the structure
of a database
• structure of a database means the data types,
relationships, and constraints that apply to the data.
– Provides means to achieve data abstraction
Categories of Data Models

https://www.youtube.com/watch?v=9qWjpVtr_Hg
Categories of Data Models
• High-level or conceptual data models
– Close to the way many users perceive data
– e.g. Entity-relationship model (ER)
• Low-level or physical data models
– Describe the details of how data is stored
on computer storage media
• Representational data models (also called
logical or implementation data models)
– Easily understood by end users
– Also similar to how data organized in
computer storage
– e.g. relational model
Schemas, Instances, and Database
State
• Database schema
– Description of a database
• Schema diagram (displayed schema)
– Displays selected aspects of schema
• Schema construct
– Each object in the schema (structure of each record)
• Database state or snapshot
– Data in database at a particular moment in time
Schema diagram & schema construct

A constraint such as
students majoring in
computer science must
take CS1310 before the
end of their sophomore
year is quite difficult to
represent
diagrammatically.
Database state / snapshot
The current set of
occurrences or instances

Data in database at a
particular moment in
time

Source: Ramez El-Masri and Shamkant Navathe


Empty state and initial state
Three-Schema Architecture
and Data Independence
• Internal level
– Describes physical storage structure of the
database
• Conceptual level
– Describes structure of the whole database for a
community of users
• External or view level
– Describes part of the database that a particular
user group is interested in
Three-Schema Architecture
and Data Independence (cont'd.)
Data Independence
• Capacity to change the schema at one level of
a database system
– Without having to change the schema at the next
higher level
• Types:
– Logical data independence
– Physical data independence
Logical data independence
The capacity to change the conceptual schema without having to change
external schemas or application programs.

Same view
(should not be affected)
Physical data independence
The capacity to change the internal schema without
having to change the conceptual schema.

For example, providing an access path to improve


retrieval speed of section records by semester and year
should not require a query such as list all sections
offered in fall 2008 to be changed, although the query
would be executed more efficiently by the DBMS by
utilizing the new access path.
Phases of database design
Centralized and Client/Server
Architectures for DBMSs
• Centralized DBMSs Architecture
– All DBMS functionality, application program
execution, and user interface processing carried
out on one machine
Database System Concepts
and Architecture
• Basic client/server DBMS architecture
– Client module
– Server module

Client module Server module, typically


handles user handles data storage,
interaction and access, search, and
provides the user- other functions.
friendly interfaces
Basic Client/Server Architectures
• Servers with specific functionalities
– File server
• Maintains the files of the client machines.
– Printer server
• Connected to various printers; all print requests by the
clients are forwarded to this machine
– Web servers or e-mail servers
Basic Client/Server Architectures
(cont'd.)
• Client machines
– Provide user with:
• Appropriate interfaces to utilize these servers
• Local processing power to run local applications
Basic Client/Server Architectures
(cont'd.)
• Client
– User machine that provides user interface
capabilities and local processing
• Server
– System containing both hardware and software
– Provides services to the client machines
• Such as file access, printing, archiving, or database
access
Two-Tier Client/Server Architectures
for DBMSs
• Server handles
– Query and transaction functionality related to SQL
processing
• Client handles
– User interface programs and application programs
Three-Tier and n-Tier Architectures for
Web Applications
• Application server or Web server
– Adds intermediate layer between client and the
database server
– Runs application programs and stores business
rules
N-tier

Divide the layers between the user and the


stored data further into finer components,
examples:
Services – such as print, directory, or
database services
Business domain – the tier that would
host Java, DCOM, CORBA, and other
application server object.
Presentation tier
Client tier – or the thin clients

You might also like