1 Database Management Systems Introduction Instructor: Oliver Schulte

Slides:



Advertisements
Similar presentations
1 Introduction to Database Systems CSE444 Instructor: Scott Vandenberg University of Washington Winter 2000.
Advertisements

Database Management Systems 1 Ramakrishnan & Gehrke Introduction to Database Systems Chapter 1 Instructor: Mirsad Hadzikadic.
Chapter 1 Instructor: Murali Mani Database Management Systems.
1 541: Database Systems S. Muthu Muthukrishnan. 2 Some Data Collections I Have Played With….  Wireless call detail records.  U. S. Patents.  AskJeeves.
Database Management Systems, R. Ramakrishnan and J. Gehrke1 Introduction to Database Systems Chapter 1 Instructor: Wang-Chien Lee
Database: A collection of related data [Elmasri]. A database represents some aspect of real world called “miniworld” [Elmasri] or “enterprise” [Ramakrishnan].
Mani-CS34311 CS3431 – Database Systems I Introduction Instructor: Murali Mani
Rundensteiner-CS34311 CS3431 – Database Systems I Introduction Instructor: Elke A. Rundensteiner
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Database Management Systems Chapter 1 Instructor: Deborah Strahman
Database Management Systems, R. Ramakrishnan and J. Gehrke1 Introduction to Database Systems Chapter 1 Instructor: Johannes Gehrke
CMPT 354, Simon Fraser University, Fall 2008, Martin Ester 1 Database Systems I Introduction.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Database Management Systems Chapter 1.
On Database Systems.
1 Introduction to Database Systems Ref. Ramakrishnan & Gehrke Chapter 1.
1 CENG 302 Introduction to Database Management Systems Nihan Kesim Çiçekli URL:
ECE 569 Database System EngineeringFall 2004 ECE 569 Database System Engineering Fall 2004 Yanyong Zhang:
Introduction overview of DBMS
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Database Management Systems Chapter 1 Instructor: Ethan Jackson
CSCD34 - Data Management Systems,- A. Vaisman1 CSC D34 - Data Management Systems Instructor: Alejandro Vaisman University of Toronto.
CSC343H – Introduction to Databases
Introduction. 
Database Management Systems 1 Introduction to Database Systems Instructor: Xintao Wu Ramakrishnan & Gehrke.
Database Management Systems, 2 nd Edition. R. Ramakrishnan and J. Gehrke1 Transaction Management Overview Chapter 18.
CS6530 Graduate-level Database Systems Prof. Feifei Li.
 DATABASE DATABASE  DATABASE ENVIRONMENT DATABASE ENVIRONMENT  WHY STUDY DATABASE WHY STUDY DATABASE  DBMS & ITS FUNCTIONS DBMS & ITS FUNCTIONS 
1 CS862 - Advanced Database Systems Sang H. Son
Database Management Systems 1 Ramakrishnan & Gehrke Introduction to Database Systems Chpt 1 Instructor: Xintao Wu.
Database Management Systems 1 Ramakrishnan & Gehrke Introduction to Database Systems Chpt 1 Instructor: Weichao Wang.
Database Management Systems
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Database Management Systems Chapter 1 Overview of Database Systems.
Database Organization and Design
DATABASE MANAGEMENT SYSTEMS TERM B. Tech II/IT II Semester UNIT-I PPT SLIDES Text Books: (1) DBMS by Raghu Ramakrishnan (2) DBMS by Sudarshan and.
INFS614, Dr. Brodsky, GMU1 Database Management Systems INFS 614 Instructor: Professor Alex Brodsky
ICS 321 Fall 2009 Introduction to Database Systems Asst. Prof. Lipyeow Lim Information & Computer Science Department University of Hawaii at Manoa.
Introduction to Database Systems1. 2 Basic Definitions Mini-world Some part of the real world about which data is stored in a database. Data Known facts.
INTRODUCTION TO DBS Database: a collection of data describing the activities of one or more related organizations DBMS: software designed to assist in.
1 What Is a DBMS?  A very large, integrated collection of data.  Models real-world enterprise.  Entities (e.g., students, courses)  Relationships (e.g.,
Database Management Systems, R. Ramakrishnan and J. Gehrke1 Introduction to Database Systems Chapter 1 Instructor: Johannes Gehrke
-ebru a.s ATTRIBUTE: Description of entities For employee entity number, name, deptno, age, adr, salary..etc are attributes. RECORD: Stores whole.
ICS 321 Spring 2011 Introduction to Database Systems Asst. Prof. Lipyeow Lim Information & Computer Science Department University of Hawaii at Manoa 1/12/20111Lipyeow.
CpSc 8620: DBMS Design Introduction. 2 Attribution Materials and lecture notes in this course are adapted from various sources, including the authors.
Intro to Database Lecture 1: Course Overview 1. 2 Data analysis in the fight against human trafficking. All of society is online. New York DA use MEMEX.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Database Management Systems Chapter 1 Professor: Iluju Kiringa
1 Geog 357: Data models and DBMS. Geographic Decision Making.
1 CS462- Database Systems Sang H. Son
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Why do you learn database?? Chapter 0.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Database Management Systems Chapter 1.
BBM 371 – Data Management Lecture 3: Basic Concepts of DBMS Prepared by: Ebru Akçapınar Sezer, Gönenç Ercan.
1 CENG 351 CENG 351 Introduction to Data Management and File Structures Department of Computer Engineering METU.
1 Introduction to Data Management Lecture #1 (Course “Trailer”) Instructor: Chen Li.
Database Management Systems 1 Ramakrishnan & Gehrke Introduction to Database Systems Chpt 1 Instructor: Xin Zhang.
COP Introduction to Database Structures
Introduction to Database Systems Chapter 1
Database Management Systems Chapter 1
Introduction to Database Systems
Instructor: Elke Rundensteiner
Database Management Systems Chapter 1
Database Management Systems Introduction
Introduction to Database Systems
Database Management Systems Introduction
Overview of Database Systems Chpt 1
Instructor: Murali Mani
Database Management Systems Chapter 1
Database Management Systems
Database Management Systems CSE594
Sang H. Son CS6750: Database Systems The slides for this text are organized into chapters. This lecture covers Chapter 1. Chapter 1: Introduction.
Introduction to Database Systems
Database Management Systems Chapter 1
Data Independence Applications insulated from how data is structured and stored. Logical data independence: Protection from changes in logical structure.
Introduction to Database Systems Chpt 1
Presentation transcript:

1 Database Management Systems Introduction Instructor: Oliver Schulte

2 Outline  What is a database?  Why use a database?  Why study databases?

3 What is a database?  A database ( DB ) is a very large, integrated, permanent collection of data.  Models real-world  Entities (e.g., students, courses)  Relationships (e.g., Madonna is taking CMPT354).  Example databases:  Customer Transactions  Human Genome  Online Bookstore  Mondial is a sample DB for teaching purposes. Mondial

4 What Is a DBMS?  A Database Management System (DBMS) is a software package designed to store and manage databases.

5 This course is important for...  End users of DBS  DB application programmers  Database administrators ( DBA )  DBMS vendors Must understand how a DBMS works!

6 Why Use Databases?

7 The Inreasing Flood of Data Online Bookstore Customer Transactions Human Genome The human genome contains 3.2 billion chemical nucleotide base pairs (A, C, T, and G). Largest known human gene is dystrophin at 2.4 million base pairs. Functions are unknown for more than 50% of discovered genes. Source: man_Genome/project/journals/insights.sht ml The human genome contains 3.2 billion chemical nucleotide base pairs (A, C, T, and G). Largest known human gene is dystrophin at 2.4 million base pairs. Functions are unknown for more than 50% of discovered genes. Source: man_Genome/project/journals/insights.sht ml As of 2004, Walmart data- warehouse was 500terabytes in size. In 2007, it was over 1petabyte (1m gigabytes) Sources: Applications/At-WalMart-Worlds-Largest- Retail-Data-Warehouse-Gets-Even-Larger/ orage/showArticle.jhtml?articleID= As of 2004, Walmart data- warehouse was 500terabytes in size. In 2007, it was over 1petabyte (1m gigabytes) Sources: Applications/At-WalMart-Worlds-Largest- Retail-Data-Warehouse-Gets-Even-Larger/ orage/showArticle.jhtml?articleID= Amazon has roughly a bazillion products, give or take a couple zillion.

8 Amazon: Website, database or application?

9 Data Storage Without DBMS File 1 File 2 File m... Application program 1 Application program 2 Application program n... reads / writes

10 Data Storage With DBMS File 1 File 2 File m... Application program 1 Application program 2 Application program n... reads / writes DBMS

11 Files vs. DBMS  Application must move large datasets between main memory and secondary storage (e.g., buffering, page-oriented access, 32-bit addressing, etc.)  Special code for different queries  Must protect data from inconsistency due to multiple concurrent users  Crash recovery  Security and access control  But note NoSQL “movement”.NoSQL

12 Why Use a DBMS? Summary  Data independence (abstract view of data) and efficient access.  Reduced application development time.  Data integrity (enforce constraints) and security.  Uniform (central) data administration.  Concurrent access, recovery from crashes.

13 Why Study Databases??  Shift from computation to information  Datasets increasing in diversity and volume.  Digital libraries, interactive video, Human Genome project ... need for DBMS exploding  DBMS intersects with most of CS  OS, languages, theory, AI, multimedia, logic ?

14 Database Overview

15 Data Models  A data model is a collection of concepts for describing data.  A schema is a description of data, using the given data model and its data definition language.  The relational model of data is the most widely used model today.  Main concept: relation, basically a table with rows and columns.  Every relation has a schema, which describes the columns, or fields.

16 Levels of Abstraction  Many views, single conceptual (logical) schema and physical schema.  Views describe how users see the data.  Conceptual schema defines logical structure  Physical schema describes the files and indexes used. * Schemas are defined using DDL = data description language. Data is modified/queried using DML = data manipulation language. Physical Schema Conceptual Schema View 1View 2View 3

17 Example: University Database  Conceptual schema:  Students(sid: string, name: string, login: string, age: integer, gpa:real)  Courses(cid: string, cname:string, credits:integer)  Enrolled(sid:string, cid:string, grade:string)  Physical schema:  Relations stored as unordered files.  Index on first column of Students.  External Schema (View):  Course_info(cid:string,enrollment:integer)

18 Data Independence  Applications insulated from how data is structured and stored.  Logical data independence : Protection from changes in logical structure of data (e.g., adding new fields).  Physical data independence : Protection from changes in physical structure of data (e.g., sorting, indexing, compressing). * One of the most important benefits of using a DBMS!

19 Review Question Data Independence In a DBMS, we can usually change the format of the data and have queries still work. E.g., divide students into full-time students and part-time students. This property is called a) logical data independence b) physical data independence. In a DBMS, we can usually change the way data is organized into files and have queries still work. E.g., move a data file from one disk to another. This property is called a) logical data independence b) physical data independence.

20 Structure of a DBMS  A typical DBMS has a layered architecture.  This is one of several possible architectures; each system has its own variations. Query Optimization and Execution Relational Operators Files and Access Methods Buffer Management Disk Space Management DB These layers must consider concurrency control and recovery

21 Review Question: Representation Which of the following plays an important role in representing information about the real world in a database? 1.The data definition language. 2.The data manipulation language. 3.The buffer manager. 4.The data model.

22 TRANSACTION PROCESSING

23 Database Transaction Processing  ACID:  Atomicity.  Consistency.  Isolation.  Durability.

24 Transaction: An Execution of a DB Program  Key concept is transaction, which is an atomic sequence of database actions (reads/writes).  Each transaction, executed completely, must leave the DB in a consistent state.

25 Concurrency Control (Isolation)  Concurrent execution of user programs is essential for good DBMS performance.  Interleaving actions of different user programs can lead to inconsistency: e.g., check is cleared while account balance is being computed.  DBMS ensures that users can pretend they are using a single-user system.

26 Scheduling Concurrent Transactions  DBMS ensures that execution of {T1,..., Tn} is equivalent to some serial execution T1’... Tn’.  Before reading/writing an object, a transaction requests a lock on the object, and waits till the DBMS gives it the lock. All locks are released at the end of the transaction.

27 Ensuring Atomicity  DBMS ensures atomicity (all-or-nothing property) even if system crashes in the middle of a Xact.  Idea: Keep a log (history) of all actions carried out by the DBMS while executing a set of Xacts:  Before a change is made to the database, the corresponding log entry is forced to a safe location. (Write-ahead log)  After a crash, the effects of partially executed transactions are undone using the log.

28 The Log  The following actions are recorded in the log:  Ti writes an object : the old value and the new value. Log record must go to disk before the changed page!  Ti commits/aborts : a log record indicating this action.  Log records chained together by Xact id, so it’s easy to undo a specific Xact (e.g., to resolve a deadlock).  Log is often duplexed and archived on “stable” storage.  All log related activities (and in fact, all CC related activities such as lock/unlock, dealing with deadlocks etc.) are handled by the DBMS.

29 Discussion: DBMS Functionality Scrooge McNugget wants to store information (names, addresses, descriptions of embarrassing moments, etc.) about the many ducks on his payroll. Not surprisingly, he wants to buy a system with the fewest possible features, and he plans to run it as a stand-alone application on his PC clone. Scrooges does not plan to share his list with anyone. Indicate which of the following DBMS features Scrooge should pay for, and why (or why not). 1. A security facility 2. Access Control 3. Concurrency Control 4. Crash recovery 5. A query language.

30 Summary: Function and Benefits  DBMS used to maintain and query permanent large datasets.  Benefits include  recovery from system crashes  concurrent access,  quick application development  data integrity  security.

31 Summary: Database Design  Levels of abstraction give data independence.  Transaction processing satisfies the ACID properties.  A DBMS typically has a layered architecture.  DBAs hold responsible jobs and are well-paid!  DBMS R&D is one of the broadest, most exciting areas in CS.