ECE 569
Database System Engineering
Spring 2003
Yanyong Zhang www.ece.rutgers.edu/~yyzhang
Course URL www.ece.rutgers.edu/~yyzhang/spring03
ECE 569 Database System Engineering
Spring 2003
About the instructor (Yanyong Zhang)

Dr./Prof. Zhang

Dr./Prof. Yanyong
Yanyong
 Office: Core 518
 Office hours: TBD (usually before class)
 Office number: 5-0608
 Email: yyzhang@ece.rutgers.edu
 URL: www.ece.rutgers.edu/~yyzhang
 Research interests:

● distributed computing
operating systems
● distributed database
●
ECE 569 Database System Engineering
Spring 2003
Something about the background

What is database?

a very large, integrated collection of data

Query

Transaction


A group of queries which possess the ACID (atomic,
consistent, isolated, and durable) property
DBMS (DataBase Management System)

a software package designed to store and manage
databases
ECE 569 Database System Engineering
Spring 2003
About the course



What will we focus on?

Transaction processing

DBMS design
What will we not focus on?

Relational data model, OO data model, etc

SQL programming
Goal

Understand DBMS design issues

Develop background for research in database area
ECE 569 Database System Engineering
Spring 2003
What should you’ve know

Data structure and algorithms

Operations system knowledge

C, Unix

Background in data model and query languages
recommended
ECE 569 Database System Engineering
Spring 2003
What will you encounter - topics

1. Relational Data Model (2-4)

2. DBMS Design / Implementation (5-11)


a) File organization (5-6)

b) Access methods (7-9)

c) Query processing (10-11)
3. Transaction Processing

a) Transaction Models (12-13)

b) Isolation (14-20)

c) Performance (21-22)

d) B-tree Synchronization (23-24)

e) Recovery (25-29)
ECE 569 Database System Engineering
Spring 2003
What will you encounter - projects

Projects

Develop a client/server relational DBMS
- Query processing / Physical data model / Data dictionary
- Concurrency control / Recovery

Work in groups of at most 4.
- You may choose groups but I must approve.
- At least three members of each group should be strong C
programmers.

Projects are difficult and time-consuming.
- ~10K lines of codes
- Use threads and RPC
- Code is difficult to debug

Projects are interesting and rewarding.
ECE 569 Database System Engineering
Spring 2003
Grading Policy

3 Homework assignments (15%)

Project (45%)

Two exams (20% each)

Course URL:
www.ece.rutgers.edu/~yyzhang/spring03
ECE 569 Database System Engineering
Spring 2003
Database Literature


Journals

IEEE Transaction on Knowledge and Data Engineering

ACM Transactions on Database Systems

VLDB Journal
Conferences

IEEE Data Engineering Conference

ACM SIGMDO

Very Large Database (VLDB)
ECE 569 Database System Engineering
Spring 2003
Time and Location


Core 538 schedule

Tuesday all day

Wednesday after 6 PM

Thursday all day
Part time students please let me know (access to
Core, and 5th floor)
ECE 569 Database System Engineering
Spring 2003
Overview

A database management system (DBMS) provides
efficient access to large amounts of persistent
data

Data models and query languages allow efficient access
while hiding complexity from users

Efficient shared access requires concurrency.
Transactions provide transparency to this concurrency.
Application programs are easier to write.

In many cases the data is valuable. It must be protected
from the effects of failure (resiliency) and sabotage
(security).
ECE 569 Database System Engineering
Spring 2003
Example – medical database

Entities in database, the types and names of their
attributes, and relationships between entities.
Date
Balance
Account
Made To
Billed
Patient
From
Address
ECE 569 Database System Engineering
Disease
Vital Sign
Time
Blood
Diagnosed
Treatment
Amount
Pulse
Name
Room#
Payment
Name
Spring 2003


Sample applications

Admit_patient

Make_diagnosis

Record_vital_signs
In relational data model we can express schema with
following tables:

patient (name, address, balance_due, room#)

payments (name, amount, date)

vital_signs (name, pulse, bp, time)

diagnosis (patient_name, disease_name)

disease (disease_name, treatment)
ECE 569 Database System Engineering
Spring 2003
Levels of Abstractions

Abstraction is used to hide complexity and allow for a separation of
concerns (What vs. How).
Subschema
definition
language
View 1
Data
definition
language
ECE 569 Database System Engineering
View 1
View 1
Specialized view
of enterprise
Conceptual Schema
Complete model
of enterprise
Physical Schema
Records,
pointers, indices
Spring 2003
Examples

Physical Level

Specify indices, e.g.,
CREATE INDEX room_index ON patient(room#);


Specify performance related characteristics of relations
Conceptual Level

Define tables, specifying data types for each attribute.
CR
CREATE TABLE patient (
name char(30),
address char(100),
balance_due number(6,2),
room# integer,
PRIMARY KEY (name));
ECE 569 Database System Engineering
Spring 2003
Examples – cont’d

External Level

Define views for various purposes, e.g.,
CREATE VIEW doctor-view-diagnosis AS
SELECT name, room#, disease_name,treatment
FROM patient, diagnosis, diseases
WHERE name = patient_name AND
diagnosis.disease_name = disease.disease_name;
ECE 569 Database System Engineering
Spring 2003
System Architecture
DDL
Statements
Interactive
Queries
Application
Program
DDL Compiler
Query
Compiler
Precompiler
Parametric
Users
Host Compiler
DML
Execute
Data
Dictionary
DML Compiler
Runtime DB
Processor
File Manager
Compiled
Transaction
Execute
Concurrency control
and recovery
DDL: Data Definition Language
 DML: Data Manipulation Language

Stored
DB
ECE 569 Database System Engineering
Spring 2003