Databases

Slides for Silberschatz-Korth-Sudarsan: DATABASE SYSTEMS CONCEPTS Lecture 1: DBMS
DataBase (Management) Systems

DBMS
Aim:
• Averall (simplified, abstract) view

• Basic notions
• Words
Notion of a Database
What is data?
What is information?
What is a Database?
ABKR=AdatBázisKezelőRendszer
DBMS=DataBaseManagementSystem
Written by Bércesné Novák, Ágnes 2003-02-03 Page 1 of 19

Notion of a Database
Huge amount of structured information which can be accessed and manipulated

efficiently through a user-friendly sofware. This structured information and the software
together can be called as DBMS. The part in which the structured information is stored is
the Database.
The DBMS is defined rather through its properties.

Properties:
1.
- New database can be constructed
- Logical structure of data can be described
Adatdefiníciós Nyelv
Data Definition Language = DDL
2.
– Data can be get back through queries efficiently
Lekérdező nyelv-Data Query Language
- Data can be modified easily
Adatmanipulációs nyelv-Data Manipulation Language (DML)

3.
- Safe storage:
- it must be defended against unauthorized users
Grants
- it must be defended against failors:
DBMS Recovery Systems
4. Concurrent usage
Transaction Management
Concurrency Control

Data(base) models
Data models serve for describing the structure of the database. The process of it is an
abstract phase, in which the first step is gathering the facts of the real world we want to
store, and also the interrelationships among these data. In the second step the facts and
properties must be represented in a standardized way in order to implement them in the
computer. This standard representation, the output of that phase, is the data model.
In a data model we do not care with the concret values of a data, rather only the
relationships among these data.
Many database can satisfy a given database model. The structured data, with the given
values, satisfying the database model is called the database instance.
The notions mentioned above will be detailed later.
WORLD abstraction DATA MODEL

Data abstraction
View 1. View 2. ..... View n.
LOGICAL/CONCEPTUAL LEVEL
PHYSICAL LEVEL
I. View level: What a user can see from the database –not the whole model can be seen (
subschemas - SDDL)
II. Logical/Conceptual level szint: The complete database model (schema - DDL),
III. Physical level: Storage and access methods, files, indeces, other storing structures

Data independence:
logical: logical level can be modified without modifying physical level
physical: physical level can be modified without modifying logical level

Example: Consider an n x m array.
Physical level: m x n (consecutive ) memory location
Logical level:
View level: 2^(m x n) possible view
Model: logical level schema
type tgrid:=array[1..2, 1..3] of integer;

var vgrid1, vgrid2:=tgrid;
An instance:
1 2 3
4 5 6

Logical/Conceptual level
Object based models:
- Entity/Relationship diagram (graphycal standard)

- Objectumoriented model, ODL (C++ like standard for describing data
structures)
Record based models:
- Relational model
- Network model
- Hierarchical model

Database modelling and implementation
Information about
world
E/R model
ODL model
Relational model
+normalization
Obj. Oriented
database
Relational
Database

History by topic
Examples:
Banking systems
User Programs:
- acoounts-deposits, withdraws
- new accounts
- balance
- monthly reports
Data items:
customers(name, address, account-no)
accounts(account-no, balance, type)
Type could be: savings or checking

(Airlines) Seat reservation systems
Data items:
customers(name, address, phone, flight-number)
flights(flight-number, departure, arrival, airport)
seats(flight-number,seat-id., name)
Company administration
- sells, bills (in-out
- what could be the data items?

File management systems
- Files could have different structures (sequential, ..)

- New questions – new programs
- Data could be stored in different storage places*which make writing new programs
difficoult
- Constraints can be hardly checked
- Atomicity level is the whole file
- Concurrency is almost impossible
- Safety can not be guaranteed
- Abstraction level is law-the programmer should know the physical level for writing
new programs

History by models
First DBMS
- network model (graph)

- hierarchical model (tree)
_______________________________
- relational model (Codd, 1970)

Who use DBMS?
Administrator:
Tasks:
- logical schema modification
- logical schema definiton
- physical schema modification
- constraints definitions
- constraints modifications
- authorization
- routine maintenance
Other users:
- programmers
- naive users
- sophisticated users

DBMS STRUCTURE
Schema definition
Storage manager (program): Query processing (progams):
- authorization and integrity manager - DDL / DML interpreter /

- file-manager compiler
- buffer manager - DML precompiler
– Query evaluation-optimization
Transaction manager (program): Physical storage (device):

- real data (the „pure” database)
Controls the correct concurrent running - metadata:
- Atomicity: all-or-none indeces
- Consistency: correctness statistical data
- Isolation: if I were alone.. data dictionary-records data structures
Tools: locking, validation, time-stamping
- Durability: ..forever…?
Tools: journal-files, mirroring..

DBMS STRUCTURE (cont.)
Klient - server architectures
DBMS simplifyied structure
Schema definitions Queries Schema modifications
Query processor
Transaction manager
Storage manager
Data, metadata


Other directions (will be partly covered):

- Object oriented database systems
- -Activev elements:
- constraints
- triggers
- Multimedia databases
- Data Warehouse

Summary
■ Database: huge amount of information

■ D B M S : 1. D D L
2. DML
3. Safety
4. Concurrency
Each part must be efficient and „easy” to use
DBMS history:
- by topic
- by model
■ DBMS structure:
- User interface
- Query Processor
- Storage manager
- Transaction manager
- Physical storage
■ New directions:
multimedia objects, data warehousing, information standards

Databases

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Databases

Încărcat de

Drepturi de autor:

Formate disponibile

Slides for Silberschatz-Korth-Sudarsan: DATABASE SYSTEMS CONCEPTS Lecture 1: DBMS

DataBase (Management) Systems

• Averall (simplified, abstract) view

Written by Bércesné Novák, Ágnes 2003-02-03 Page 1 of 19

Huge amount of structured information which can be accessed and manipulated

The DBMS is defined rather through its properties.

Written by Bércesné Novák, Ágnes 2003-02-03 Page 2 of 19

Written by Bércesné Novák, Ágnes 2003-02-03 Page 3 of 19

The notions mentioned above will be detailed later.

WORLD abstraction DATA MODEL

Written by Bércesné Novák, Ágnes 2003-02-03 Page 4 of 19

View 1. View 2. ..... View n.

Written by Bércesné Novák, Ágnes 2003-02-03 Page 5 of 19

logical: logical level can be modified without modifying physical level

physical: physical level can be modified without modifying logical level

Written by Bércesné Novák, Ágnes 2003-02-03 Page 6 of 19

Example: Consider an n x m array.

Physical level: m x n (consecutive ) memory location

View level: 2^(m x n) possible view

Model: logical level schema

type tgrid:=array[1..2, 1..3] of integer;

Written by Bércesné Novák, Ágnes 2003-02-03 Page 7 of 19

Object based models:

- Entity/Relationship diagram (graphycal standard)

Record based models:

Written by Bércesné Novák, Ágnes 2003-02-03 Page 8 of 19

Database modelling and implementation

Written by Bércesné Novák, Ágnes 2003-02-03 Page 9 of 19

Written by Bércesné Novák, Ágnes 2003-02-03 Page 10 of 19

(Airlines) Seat reservation systems

Written by Bércesné Novák, Ágnes 2003-02-03 Page 11 of 19

File management systems

- Files could have different structures (sequential, ..)

Written by Bércesné Novák, Ágnes 2003-02-03 Page 12 of 19

- network model (graph)

- relational model (Codd, 1970)

Written by Bércesné Novák, Ágnes 2003-02-03 Page 13 of 19

Who use DBMS?

Written by Bércesné Novák, Ágnes 2003-02-03 Page 14 of 19

- authorization and integrity manager - DDL / DML interpreter /

Transaction manager (program): Physical storage (device):

Written by Bércesné Novák, Ágnes 2003-02-03 Page 15 of 19

DBMS STRUCTURE (cont.)

Klient - server architectures

DBMS simplifyied structure

Schema definitions Queries Schema modifications

Written by Bércesné Novák, Ágnes 2003-02-03 Page 16 of 19

Written by Bércesné Novák, Ágnes 2003-02-03 Page 17 of 19

Other directions (will be partly covered):

Written by Bércesné Novák, Ágnes 2003-02-03 Page 18 of 19

■ Database: huge amount of information

Written by Bércesné Novák, Ágnes 2003-02-03 Page 19 of 19

S-ar putea să vă placă și