Académique Documents
Professionnel Documents
Culture Documents
Initial Definitions
Database Characteristics
• Persistent
– data residing on stable storage, not a temporary storage such as computer memory (Textbook’s
definition) ← relevance of intended usage
– Stored data can subsequently be removed from the database only by some explicit request to the
database management system, not as a side effect of a program execution. (C.J. Date’s definition)
– Lasts a long time (not transient). (e.x., birth date vs. age)
• Interrelated
– separate data units connected to provide a broader view
– entity: cluster of data about a topic (customer, student, loan)
– relationship: connection among entities
• Shared
– by multiple applications and users (maybe at the same time)
– a database as a common information repository and information exchange platform (file processing
vs. database approaches)
Faculty
Registration
Entities: Assignment
students, faculty, courses,
offerings, enrollments
Relationships:
faculty teach offerings,
Grade students enroll in Course
Recording offerings, offerings made Scheduling
of courses, ...
University Database
Features of DBMS
Data Definition
• Graphical tools
PK StdNo PK OfferNo
Faculty
StdFirstName FK2 CourseNo
StdLastName FK1 FacNo PK FacNo
StdCity OffLocation
Teaches FacFirstName
StdState OffYear
StdZip OffTerm FacLastName
StdMajor OffDay FacCity
StdClass OffTime FacState
StdGPA FacZip
FacDept
Accepts FacRank
has FacSalary
Registers FK1 FacSupervisor
FacHireDate
Enrollment Course
• Graphical tools
Application Development
• Examples
– Java or Visual Basic programming over a database
– Web database publishing
Transaction Processing
Database Tuning
DBMS Marketplace
• Enterprise DBMS
– Oracle: dominates in Unix; strong in Windows
– SQL Server: strong in Windows
– DB2: dominates in mainframe
– Teradata: as a data warehouse platform
– Significant open source systems: MySQL, Firebird, PostgreSQL
• Desktop DBMS
– Access: dominates
Data Independence
External
View 1 View 2 View n Level
External to
Conceptual
Conceptual Conceptual
Mappings
Schema Level
Conceptual
to Internal
Mappings Internal
Internal Level
Schema
• External
– Faculty Assignment Form View: data required for the form in Slide 12
– Faculty Work Load Report View: data required for the report in Slide 13
• Internal
– Files needed to store the tables
– Extra files to improve performance
– The whole database from the point of view of hardware and physical
processing
Client-Server Architecture
a) Client-server processing with database server b) Client-server processing with middleware and database servers
Database Database
Database Middleware Database
server server server
(a) SD (b) SN
N N
P P ... P P P ... P
M M M M M M
... ...
Legend
P: processor
M: memory
N: high-speed network
SD: shared disk
SN: shared nothing
Tokyo
Client Server
Client Database
Denver London
Client Server Server Client
Client Client
Database Database
Cloud Computing
Server
Database
Server Server
Database Database
Database Specialists
• Data administrator
– Less technical
– Planning role
– Information resource management
DBA Responsibilities
Technical Non-technical
Designing conceptual schemas Setting database standards
Designing internal schemas Devising training materials
Monitoring database performance Promoting benefits of
databases
Selecting and evaluating database Consulting with users
software