2003-10-06
DATABASTEKNIK - 1DL116Hösten 2003 |
Johan Petrini, labassistent
epost: johan.petrini@it.uu.se,
tel: 471 6345, rum 1316
Milena Koparanova, labassistent
epost: milena.koparanova@it.uu.se,
tel: 471 2846, rum 1316
SCHEDULE
Dag: Datum: Fö: Tid: Sal: Innehåll:
V43
Torsdag 23/10 F1 10-12 1311 Intro DB terminologi (EN kap 1,2) KO
Fredag 24/10 F2 10-12 1311 ER/EER-modellering (EN kap 3,4) KO
V44
Måndag 27/10 F3 13-15 1311 Relationsmodellen - relationsalgebra KO
Onsdag 29/10 F4 13-15 1111 Fysisk databasdesign - normalisering, ex normalisering KO
V45
Måndag 3/11 F5 13-15 Å2001 SQL intro KO
Fredag 7/11 F6 13-15 1111 SQL forts KO
V46
Måndag 10/11 F7 13-15 1211 Transaktioner, concurrency control KO
Onsdag 12/11 F8 10-12 1211 Recovery KO
Fredag 14/11 F9 13-15 1211 Fysisk databasdesign - lagringsstrukturer och index KO
V47
Måndag 17/11 F10 10-12 1211 Fysisk databasdesign - fortsättning KO
Onsdag 19/11 F11 10-12 1211 Säkerhet och dataintegritet TR
Fredag 21/11 F12 13-15 1211 Procedurell SQL och SQL applikationsgränssnitt TR
V48
Tisdag 25/11 F13 13-15 1311 Aktiva databaser TR
Torsdag 27/11 F14 10-12 6140 Objektdatabaser TR
V49
Måndag 1/12 F15 10-12 1211 Objekt-relationella databser, AmosQL TR
Torsdag 4/12 F16 13-15 1111 AmosQL forts TR
Fredag 5/12 F17 10-12 1311 Relationskalkyl TR
V50
Måndag 8/12 F18 10-12 1211 Frågeoptimering TR
Onsdag 10/12 F19 10-12 1311 Data wharehousing TR
Torsdag 11/12 F20 13-15 1111 Gästföreläsning
V51
Tisdag 16/12 F21 10-12 1211 Multimedia och spatiala db TR
Torsdag 18/12 Tentamen 08-13 Skrivsalen, Polacksbacken
If you are going to create a data base that models part of the real world, for example a company or some other organisation, the first step is usually to make a description of the structure and function of that part of the real world, i. e. a conceptual data model. In this course we will learn, and use, a method called Entity-Relationship modeling.
The conceptual model actually has nothing at all to do with computers, since it is just a description of the world, which could equally well be used e. g. by someone who needs to study the internal functioning of the company. If you want to create a database in a computer you must first translate the conceptual data model to an implementation data model, which is then used to implement the data base. There are several different classes of implementation data models, and in this course we will study the relational and object-oriented models. The emphasis is on the relational model.
A database is a collection of data. It is usually managed by a special program or program system, called a database management system, DBMS for short. During the course we will study how a DBMS is structured and how it functions, among other things how it stores its data internally, how it prevents unauthorized access to the data, and how it solves the problems that arise when several users simultaneously want to look at or change the data.
Since we want to access the database, i. e. ask questions about the
data,
change the data, or define which data that are to be stored, the
database
management system provides several interfaces, for example a query
language.
We will look at some of these interfaces, mostly for the relational
model.
The emphasis is on the query language SQL, and also on an
object-oriented
dialect of SQL. We will also study some modern database technologies,
such
as active and multimedia databases, and we will also have a look at
data
warehousing.
This course is organised as a series of lectures, with an accompanying series of exercises (labs) to be solved with the help of the computer. The practical excercises are made by the students on their own with some assistance from the course assistants.
Most of the course contents will be covered in the lectures and in the exercises, but it is nevertheless necessary to use your own time to read the course literature and to work with the course material and the computer.
Chapter 1: All. Read 1.4 and 1.5 on your own.
Chapter 2: All. Read 2.5 on your own.
Chapter 3: All.
Chapter 4: All. Read 4.5 on your own.
Chapter 5: All.
Chapter 6: All.
Chapter 7: All except 7.2.
Chapter 8: All. General knowledge about functionality in SQL is required. You shall be able to formulate
a query given a database schema and be able to use constructs covered in lectures and labs.
Chapter 9: All except 9.4.4 and 9.4.5
Chapter 10: All except 10.2.2, 10.2.3, 10.2.4.
Chapter 11: Omitted.
Chapter 12: Omitted.
Chapter 13: Read Ch. 13.1-13.3 if you need an introduction to disk storage.
Read Ch. 13.3-13.8 to the extension that is required to understand the principles for file-organization and
indexing techniques.
Skip Ch. 13.9-13.11.
Chapter 14: Read to the extension that is required to understand the principles for file-organization and
indexing techniques.
Skip Ch. 14.4-14.5.
Chapter 15:All except 15.4, 15.5, 15.7, 15.9, 15.10
Covered by compendium in Swedish.
Chapter 16: Omitted.
Chapter 17: Ch. 17.5 omitted. Note! However, you should know what is meant by the concepts
serial, non-serial, and serializable transaction schedule.
Chapter 18: Ch. 18.2, 18.3, 18.6, 18.7 omitted.
Chapter 19: Ch. 19.5, 19.6 omitted.
Chapter 20: Skip 20.2.2, 20.2.3, 20.3.2, 20.6.
General knowledge about object-oriented concepts to understand the distributed slides fully.
Chapter 21: Omitted.
Chapter 22: Omitted.
Chapter 23: Skip 23.3 - 23.6
Chapter 24: Read 24.1, 24.3 only.
Chapter 25: Omitted.
Chapter 26: Omitted.
Chapter 27: Omitted.
Chapter 28: Read 28.
Chapter 29: Read 29.2. Read 29.3-29.4 on your own.
OH-BILDER OCH KOMPENDIER
F1: Intro till DB terminologi (som *.pdf)INSTRUCTIONS TO,
AND
MATERIAL FOR, EXERCISES