Lecture 02 The Relational Data Model. Advantages of Database.

Slides:



Advertisements
Similar presentations
Chapter IV Relational Data Model Pemrograman Sistem Basis Data.
Advertisements

Chapter 3 : Relational Model
Chapter 1: The Database Environment
Chapter 3 The Relational Model Transparencies © Pearson Education Limited 1995, 2005.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 3 The Basic (Flat) Relational Model.
Chapter 3. 2 Chapter 3 - Objectives Terminology of relational model. Terminology of relational model. How tables are used to represent data. How tables.
Introduction to Databases Transparencies
1 Minggu 2, Pertemuan 3 The Relational Model Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
1 Pertemuan 04 MODEL RELASIONAL Matakuliah: >/ > Tahun: > Versi: >
Chapter 1 Introduction to Databases
Data at the Core of the Enterprise. Objectives  Define of database systems  Introduce data modeling and SQL  Discuss emerging requirements of database.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Chapter 1 1 © Prentice Hall, 2002 Database Design Dr. Bijoy Bordoloi Introduction to Database Processing.
IST Databases and DBMSs Todd S. Bacastow January 2005.
Chapter 1 1 © Prentice Hall, 2002 Database Design Dr. Bijoy Bordoloi Introduction to Database Processing.
Lecture 2 The Relational Model. Objectives Terminology of relational model. How tables are used to represent data. Connection between mathematical relations.
Chapter 4 The Relational Model Pearson Education © 2014.
Relational Model Session 6 Course Name: Database System Year : 2012.
Chapter 4 The Relational Model.
Chapter 3 The Relational Model Transparencies Last Updated: Pebruari 2011 By M. Arief
Data at the Core of the Enterprise. Objectives  Define of database systems.  Introduce data modeling and SQL.  Discuss emerging requirements of database.
CS370 Spring 2007 CS 370 Database Systems Lecture 2 Overview of Database Systems.
STORING ORGANIZATIONAL INFORMATION— DATABASES CIS 429—Chapter 7.
Chapter One (Introduction) Objectives Introduction to Database Management Systems (DBMS) Relational Databases Model Restrictions of RD Database Life Cycle.
THE RELATIONAL DATA MODEL CHAPTER 3 (6/E) CHAPTER 5 (5/E) 1.
Chapter 3 The Relational Model. 2 Chapter 3 - Objectives u Terminology of relational model. u How tables are used to represent data. u Connection between.
Database System Concepts, 6 th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 2: Intro to Relational.
Chapter 2 Adapted from Silberschatz, et al. CHECK SLIDE 16.
Copyright © Curt Hill The Relational Model of Database Basic organization and terms.
1 The Relational Database Model. 2 Learning Objectives Terminology of relational model. How tables are used to represent data. Connection between mathematical.
9/7/2012ISC329 Isabelle Bichindaritz1 The Relational Database Model.
Instructor: Dema Alorini Database Fundamentals IS 422 Section: 7|1.
The Relational Model Pertemuan 03 Matakuliah: M0564 /Pengantar Sistem Basis Data Tahun : 2008.
Relational Database. Database Management System (DBMS)
Lecture # 3 & 4 Chapter # 2 Database System Concepts and Architecture Muhammad Emran Database Systems 1.
Module Coordinator Tan Szu Tak School of Information and Communication Technology, Politeknik Brunei Semester
Chapter One (Database System) Objectives Introduction to Database Management Systems (DBMS) Data and Information History of DB Types of DB.
Chapter 2: Intro to Relational Model. 2.2 Example of a Relation attributes (or columns) tuples (or rows)
Database System Concepts, 6 th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 2: Introduction.
CS 338The Relational Model2-1 The Relational Model Lecture Topics Overview of SQL Underlying relational model Relational database structure SQL DDL and.
CSE314 Database Systems Lecture 3 The Relational Data Model and Relational Database Constraints Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson.
The Relational Model. 2 Relational Model Terminology u A relation is a table with columns and rows. –Only applies to logical structure of the database,
Introduction to Databases
Jennifer Widom Relational Databases The Relational Model.
The Relational Model © Pearson Education Limited 1995, 2005 Bayu Adhi Tama, M.T.I.
The relational model1 The relational model Mathematical basis for relational databases.
CSCI 6315 Applied Database Systems Review for Midterm Exam I Xiang Lian The University of Texas Rio Grande Valley Edinburg, TX 78539
Chapter 3 The Relational Model. Objectives u Terminology of relational model. u How tables are used to represent data. u Connection between mathematical.
Chapter 4 The Relational Model Pearson Education © 2009.
LECTURE TWO Introduction to Databases: Data models Relational database concepts Introduction to DDL & DML.
Databases and DBMSs Todd S. Bacastow January
Introduction to Databases
Chapter 2: Intro to Relational Model
The Relational Database Model
Data Base System Lecture 6: Relational Model
Chapter 3 The Relational Model.
Chapter 4 The Relational Model Pearson Education © 2009.
Chapter 4 The Relational Model Pearson Education © 2009.
Relational Databases The Relational Model.
Relational Databases The Relational Model.
Chapter 4 The Relational Model Pearson Education © 2009.
The Relational Model Textbook /7/2018.
The Relational Model Transparencies
Chapter 4 The Relational Model Pearson Education © 2009.
Chapter 4 The Relational Model Pearson Education © 2009.
Chapter 2: Intro to Relational Model
Chapter 4 The Relational Model Pearson Education © 2009.
The Database Environment
The Relational Data Model
Chapter 3 The Relational Model
Presentation transcript:

Lecture 02 The Relational Data Model

Advantages of Database

Data Consistency Better Data Security Faster Application Development Economy of Scale Better Concurrency Control Better Backup and Recovery Facility

The Range of Database Applications Personal Database – standalone desktop database Workgroup Database – local area network (<25 users) Department Database – local area network ( users) Enterprise Database – wide-area network (hundreds or thousands of users)

Models, Schemas and States A data model defines the constructs available for defining a schema – defines possible schemas A schema defines the constructs available for storing the data – defines database structure – limits the possible database states A database state (or instance) is all the data at some point in time the database content

Models, Schemas and States data model – fixed by the DBMS schema – defined by the DB designer – generally fixed once defined * database state – changes over time due to user updates * schema modifications are possible once the database is populated, but this generally causes difficulties

RELATION SCHEMAS AND RELATION INSTANCES

Relation Schemas A relation is defined by a name and a set of attributes Each attribute has a name and a domain – a domain is a set of possible values – all domains are sets of atomic values – RDM does not recommend complex data types – domains may contain a special null value

Definition: Relation Schema Relation Schema – R is the relation name – A 1 … A n are the attribute names Domains are denoted by degree = the number of attributes R(A 1, A 2, …, A n ) dom(A i )

Characteristics of Relations A relation is a set – tuples are unordered – no duplicate tuples Attribute values within tuples are ordered – values are matched to attributes by position – alternate definition defines a tuple as a set of (name,value) pairs, which makes ordering of tuple unnecessary (we won’t use this definition)

Characteristics of Relations Values in tuples are atomic Each Column has distinct name The values of the attribute come from the same domain The order of the column is immaterial Each row/tuple/record is distinct

SQL: Relation States A relation is viewed as a table The attributes define the columns of the table Each row in the table holds related values for each attribute – a row often represents a conceptual entity (object) Values in each column must come from the domain of the attribute – the values are instances of the attribute type

Example Schema