Database Environment Pertemuan 02 Matakuliah: M0564 /Pengantar Sistem Basis Data Tahun : 2008.

Slides:



Advertisements
Similar presentations
1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
Advertisements

Introduction to Databases
1 Chapter 2 Database Environment Transparencies © Pearson Education Limited 1995, 2005.
1 Pertemuan 02 Database environment Matakuliah: >/ > Tahun: > Versi: >
Chapter 2 Database Environment.
1 Pertemuan 01 Pengantar tentang database Matakuliah: >/ > Tahun: > Versi: >
Chapter 2 Database Environment. Agenda Three-Level ANSI-SPARC Architecture Database Languages Data Models Functions of DBMS Components of DBMS Teleprocessing.
1 Minggu 1, Pertemuan 1 Introduction to Database Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
Data Management I DBMS Relational Systems. Overview u Introduction u DBMS –components –types u Relational Model –characteristics –implementation u Physical.
Chapter 2 Database Environment Pearson Education © 2014.
1 Chapter 2 Database Environment. 2 Objectives of Three-Level Architecture u All users should be able to access same data u User’s view immune to changes.
Lecture Two Database Environment Based on Chapter Two of this book:
1 Chapter 2 Database Environment. 2 Chapter 2 - Objectives u Purpose of three-level database architecture. u Contents of external, conceptual, and internal.
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
Database Environment 1.  Purpose of three-level database architecture.  Contents of external, conceptual, and internal levels.  Purpose of external/conceptual.
1 Chapter 2 Database Environment Transparencies Last Updated: Pebruari 2010 By M. Arief Updated by RSO Feb 2011
Database System Concepts and Architecture Lecture # 3 22 June 2012 National University of Computer and Emerging Sciences.
Chapter 2 CIS Sungchul Hong
Chapter 2 Database Environment
CSC271 Database Systems Lecture # 4.
CST203-2 Database Management Systems Lecture 2. One Tier Architecture Eg: In this scenario, a workgroup database is stored in a shared location on a single.
Database Environment Chapter 2 AIT632 Sungchul Hong.
Database System Concepts and Architecture
9/5/2012ISC329 Isabelle Bichindaritz1 Web Database Environment.
Lecture On Introduction (DBMS) By- Jesmin Akhter Assistant Professor, IIT, Jahangirnagar University.
1 Chapter 2 Database Environment Transparencies © Pearson Education Limited 1995, 2005.
Lecture2: Database Environment Prepared by L. Nouf Almujally & Aisha AlArfaj 1 Ref. Chapter2 College of Computer and Information Sciences - Information.
Chapter 2 Database Environment. Agenda Three-Level ANSI-SPARC Architecture Database Languages Data Models Functions of DBMS Components of DBMS Data Dictionary.
Lecture2: Database Environment Prepared by L. Nouf Almujally 1 Ref. Chapter2 Lecture2.
The Relational Model Pertemuan 03 Matakuliah: M0564 /Pengantar Sistem Basis Data Tahun : 2008.
Database Systems DBMS Environment Data Abstraction.
8/31/2012ISC329 Isabelle Bichindaritz1 Database Environment.
Database Environment Chapter 2. Data Independence Sometimes the way data are physically organized depends on the requirements of the application. Result:
1 Database Management Systems (DBMS). 2 Database Management Systems (DBMS) n Overview of: ä Database Management Components ä Database Systems Architecture.
Module 2: Database Environment
Bayu Adhi Tama, M.T.I 1 © Pearson Education Limited 1995, 2005.
Database Environment Session 2 Course Name: Database System Year : 2013.
1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
Chapter 2 Database Environment Chuan Li 1 © Pearson Education Limited 1995, 2005.
1 Chapter 1 Introduction to Databases Transparencies.
1 Lecturer M.Eng. Nguyen Ngo Bao Tran URL:
1 Database Environment. 2 Objectives of Three-Level Architecture All users should be able to access same data. A user’s view is immune to changes made.
Chapter 2 Database Environment.
1 Database Environment. 2 Objectives of Three-Level Architecture u All users should be able to access same data. u A user’s view is immune to changes.
1 Chapter 2 Database Environment Pearson Education © 2009.
Lecture On Introduction (DBMS) By- Jesmin Akhter Assistant Professor, IIT, Jahangirnagar University.
Database Environment CPSC 356 Database Ellen Walker Hiram College.
Database Environment Chapter 2. The Three-Level ANSI-SPARC Architecture External Level Conceptual Level Internal Level Physical Data.
CENG 352 Database Management Systems Nihan Kesim Çiçekli URL:
CS-508 Databases and Data Mining By Dr. Noman Hasany.
國立臺北科技大學 課程:資料庫系統 Chapter 2 Database Environment.
REV 00 Chapter 2 Database Environment DDC DATABASE SYSTEM.
Introduction to Databases
REV 00 Chapter 2 Database Environment DDC DATABASE SYSTEM.
Chapter 2 Database Environment.
COMSATS INSTITUTE OF INFORMATION TECHNOLOGY, VEHARI
Tahun : <<2005>> Versi : <<1/1>>
Introduction to Databases
Introduction to Databases
Chapter 2 Database Environment.
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment.
Data Base System Lecture : Database Environment
Database Environment Transparencies
Introduction to Databases
Chapter 2 Database Environment Pearson Education © 2014.
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment Pearson Education © 2009.
Presentation transcript:

Database Environment Pertemuan 02 Matakuliah: M0564 /Pengantar Sistem Basis Data Tahun : 2008

Bina Nusantara Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu : Mahasiswa dapat menerangkan tujuan dari database dan penjelasan akan hubungan, cara penyimpanan serta manipulasi data (C2) Learning Outcomes 3

Bina Nusantara Acknowledgments These slides have been adapted from Thomas Connolly and Carolyn Begg

Bina Nusantara ANSI-SPARC Architecture Database Languages Data Models and Conceptual Modeling Functions and Component of a DBMS Multi-User DBMS Architectures Outline Materi 5

Bina Nusantara Objectives of Three-Level Architecture All users should be able to access same data. A user’s view is immune to changes made in other views. Users should not need to know physical database storage details. DBA should be able to change database storage structures without affecting the users’ views. Internal structure of database should be unaffected by changes to physical aspects of storage. DBA should be able to change conceptual structure of database without affecting all users.

Bina Nusantara ANSI-SPARC Three-Level Architecture

Bina Nusantara ANSI-SPARC Three-Level Architecture External Level –Users’ view of the database. –Describes that part of database that is relevant to a particular user. Conceptual Level –Community view of the database. –Describes what data is stored in database and relationships among the data. Internal Level –Physical representation of the database on the computer. –Describes how the data is stored in the database.

Bina Nusantara Differences between Three Levels of ANSI- SPARC Architecture

Bina Nusantara Data Independence Logical Data Independence –Refers to immunity of external schemas to changes in conceptual schema. –Conceptual schema changes (e.g. addition/removal of entities). –Should not require changes to external schema or rewrites of application programs. Physical Data Independence –Refers to immunity of conceptual schema to changes in the internal schema. –Internal schema changes (e.g. using different file organizations, storage structures/devices). –Should not require change to conceptual or external schemas.

Bina Nusantara Data Independence and the ANSI-SPARC Three-Level Architecture

Bina Nusantara Database Languages Data Definition Language (DDL) –Allows the DBA or user to describe and name entities, attributes, and relationships required for the application –plus any associated integrity and security constraints. Data Manipulation Language (DML) –Provides basic data manipulation operations on data held in the database. Procedural DML –allows user to tell system exactly how to manipulate data. Non-Procedural DML –allows user to state what data is needed rather than how it is to be retrieved.

Bina Nusantara Database Languages Fourth Generation Language (4GL) –Query Languages –Forms Generators –Report Generators –Graphics Generators –Application Generators.

Bina Nusantara Data Model Integrated collection of concepts for describing data, relationships between data, and constraints on the data in an organization. Data Model comprises: –a structural part; –a manipulative part; –possibly a set of integrity rules. Purpose –To represent data in an understandable way. Categories of data models include: –Object-based –Record-based –Physical.

Bina Nusantara Data Models Object-Based Data Models –Entity-Relationship –Semantic –Functional –Object-Oriented. Record-Based Data Models –Relational Data Model –Network Data Model –Hierarchical Data Model. Physical Data Models

Bina Nusantara Conceptual Modeling Conceptual schema is the core of a system supporting all user views. Should be complete and accurate representation of an organization’s data requirements. Conceptual modeling is process of developing a model of information use that is independent of implementation details. Result is a conceptual data model.

Bina Nusantara Functions of a DBMS Data Storage, Retrieval, and Update. A User-Accessible Catalog. Transaction Support. Concurrency Control Services. Recovery Services. Authorization Services. Support for Data Communication. Integrity Services. Services to Promote Data Independence. Utility Services.

Bina Nusantara Components of a DBMS

Bina Nusantara Components of Database Manager (DM)

Bina Nusantara Multi-User DBMS Architectures Teleprocessing File-server Client-server

Bina Nusantara Teleprocessing Traditional architecture. Single mainframe with a number of terminals attached. Trend is now towards downsizing.

Bina Nusantara Teleprocessing Topology

Bina Nusantara File-Server File-server is connected to several workstations across a network. Database resides on file-server. DBMS and applications run on each workstation. Disadvantages include: –Significant network traffic. –Copy of DBMS on each workstation. –Concurrency, recovery and integrity control more complex.

Bina Nusantara File-Server Architecture

Bina Nusantara Client-Server Server holds the database and the DBMS. Client manages user interface and runs applications. Advantages include: –wider access to existing databases; –increased performance; –possible reduction in hardware costs; –reduction in communication costs; –increased consistency.

Bina Nusantara Client-Server Architecture

Bina Nusantara Alternative Client-Server Topologies

Bina Nusantara Transaction Processing Monitors Program that controls data transfer between clients and servers in order to provide a consistent environment, particularly for Online Transaction Processing (OLTP).

Bina Nusantara Transaction Processing Monitor as middle tier of a three-tier client-server architecture

Bina Nusantara System Catalog Repository of information (metadata) describing the data in the database. Typically stores: –names of authorized users; –names of data items in the database; –constraints on each data item; –data items accessible by a user and the type of access. Used by modules such as Authorization Control and Integrity Checker.

Bina Nusantara Information Resource Dictionary System (IRDS) Response to an attempt to standardize data dictionary interfaces. Objectives: –extensibility of data; –integrity of data; –controlled access to data.

Bina Nusantara IRDS services interface

Bina Nusantara Dilanjutkan ke pert. 03 The Relational Model